I sort of run into the same problem here. It looks like some configuration error. Does anyone know if there is any extra config needed for Acegi with JAAS?
Type: Posts; User: good12; Keyword(s):
I sort of run into the same problem here. It looks like some configuration error. Does anyone know if there is any extra config needed for Acegi with JAAS?
Anyone has a clue of this? It seems closely related to the specific AOP proxy implementation logic in Spring. It does not matter whether you restrict the class name like: * package.someclass. As long...
That's exactly what heppened - the advice got advised on. What I was trying to do was implementing a simple method level execution trace log. It turns out I have to use a pointcut expression...
For the above case, there is a logging aspect defined on the dataSource bean. The error happens only when this AOP on the dataSource bean is enabled. Is this because the sequence of the dataSource...
I'm using Spring 2.0.6 and run into another interesting issue.
When I:
1) use xml schema-based AOP configuration
2) define a broad pointcut expression like * *(..)
3) define one "before" advice...
I'm using spring 2.0.6 and got the following interesting stuff:
When I:
1) use AOP with jdk interface proxy (which means do not force it to use CGLIB)
2) use xml schema-based AOP defining
3)...
I'm using Spring 2.0.6 and got a question regarding AOP:
When I define 2 transactionAdvisor beans in the same ApplicationContext- one uses jdbc transactionManager, the other uses hibernate...