Search:

For the sake of symmetry you can also declare two AuthenticationProcessingFilter beans (one for each area) and then neuter the one in the declarative http section like this:

...

I'm just wondering if there has been any progress on this front (updating Acegi for Spring 2.x). Unfortunately the work I did was for a closed project, so in order to contribute it I'd have to...

The solution that I eventually found was to go ahead and write a Spring 2.0 aspecj style aspect that implements the Acegi AbstractSecurityInterceptor. The pointcut refers to the @Secured annotation...

So, to recap - If I try to mix the old style acegi method interceptor / autoproxy bean factory with the new style declarative transactions and aspectj autoproxy things don't work. They work...

Ah. Yes, my problem seems to be in how to mix the two. I think the docs explicitly warn not to mix the aspectj-autoproxy and the explicit aop config...


thanks,
Pat

Well, actually this looks promising. Is your logging component an aspectj advisor or an AOPAlliance method interceptor?


Pat

I am currently using Spring 2.0 with the <aop:aspectj-autoproxy> and <tx:annotation-driven> transactions. I have been able to get acegi method interception working by using an old style autoproxy...

I too was surprised to find that I could not put annotations on interface methods because Spring explicitly allow this for @Transactional. It's just not very Spring-like behavior to make interfaces...

Yes, thanks. You might want to confirm that your code works with 2.0 RC4. The situation appeared for me in just the final 2.0 release.

That might help narrow it down.


Pat

I have some methods that are annotated with @Transactional and my own spring AOP annotation. After upgrading to Spring 2.0 I get the following exception regarding argument binding. I have seen...

There seems to be an issue in mixing the declarative transactions with aspectj aop support:

<tx:annotation-driven/>
<aop:aspectj-autoproxy/>

I have a logging aspect that uses a...

Upgrading to the Aspectj 1.5.2 libs solved the problem for me.

thanks,
Pat

that should have read:

@Around( "@annotation(myAnnotation)" )
public Object doSomething(
ProceedingJoinPoint pjp, MyAnnotation myAnnotation ) { }


Pat

Is it possible to get access to the annotation used in an @Around pointcut? I would have expected this to work:

@Around("@annotation("myAnnotation")
public Object doSomething(...

Ok, after a little experimentation I think I have the answer.

Do *not* use the <tx:annotation-driven>. Instead specify <tx:advice> and refer to that in an <aop:config> block to govern which...

I'd like to use annotation based transactions with hibernate as described in 2.0, however I have more than one session factory and consequently more than one transaction manager. Obviously I'd have...