spring-aop

in one dao I have 2 @Transactional methods. if i do not provide any explicit properties, then what will happen, if I run one method in the body of another? Both methods will run within THE SAME ONE TRANSACTION? Proxies in Spring AOP When using Transactional, you're dealing with proxies of classes, so in this scenario: @Transactional public void doSomeThing(){ // calling this method targets a proxy doSomeThingElse(); // this method targets the actual class, not the PROXY, // so the transactional annotation has no effect } @Transactional public void doSomeThingElse(){ } you are calling the proxy

I need a pointcut for methods in classes annotated with @X or methods annotated with @X . I also need the annotation object . If both the class and the method are annotated I prefer to get the method annotation as argument . I tried the following, which creates an "inconsistent binding" warning. (Why not just set them null?) @Around("@annotation(methodLevelX) || @within(classLevelX)") public Object advise(ProceedingJoinPoint pjp, X methodLevelX, X classLevelX) The following creates a "ambiguous binding of parameter(s) x across '||' in pointcut" warning. (Which does not necessarily make sense

I'm reading up on Spring at the moment and one of the examples used for a use of AOP is logging the start and end of method calls. I've also read that using AOP can impact performance. Is using Spring AOP a good idea for this type of logging? My understanding is that Spring uses Dynamic AOP would it be be better to use Static AOP (Like AspectJ) for this type of AOP. Curently the coding policy of the company I work for requires a ridiculous amount of logging and i want to reduce the ammount of logging code I have to write and improve the readability of my code. Am I barking up the wrong tree?

Anyone knows why apparently it is not possible to use AOP with annotated MVC Controllers? (see Post ). I have a @Controller that stops working as soon as I add a pointcut to it. The problem is not that the interceptor is not being called, but rather the @Controller simply stops working (in the log you can see that instead of "Mapped URL path [/xx] onto handler 'Yyy'" you get a "no URL paths identified"). I know there is a mechanism for adding interceptors to controllers via the handlerMapping but my question is specific to AOP interceptors. Aren't annotated controllers just pojos in the Spring

We have started to use spring aop for cross cutting aspects of our application (security & caching at the moment). My manager worries about the performance impact of this technology although he fully understands the benefits. My question, did you encounter performance problems introduced by the use of aop (specifically spring aop)? As long as you have control of your AOP I think it's efficient. We did have performance problems anyway, so by own reasoning we were not fully in control ;) This was mostly because it's important that anyone that writes aspects has full understanding of all the

I am moving from an xml config to annoations. i want to convert a session scoped bean that is <aop:scoped-proxy> can this be done with annotations, and if not, what can i do to still keep that declaration working? edit: I am interested in doing this in Spring 2.5 in the spring context xml, do something like: <context:component-scan base-package="com.startup.failure" scoped-proxy="interfaces" /> Note that you would need to write interfaces for all classes in that package, though. In Spring 3.0 it can be specified by the proxyMode attribute of @Scope annotation: @Scope(value = "session",