spring-aop

I am using Spring's declarative transactions (the @Transactional annotation) in "aspectj" mode. It works in most cases exactly like it should, but for one it doesn't. We can call it Lang (because that's what it's actually called). I have been able to pinpoint the problem to the load time weaver. By turning on debug and verbose logging in aop.xml, it lists all classes being woven. The problematic class Lang is indeed not mentioned in the logs at all. Then I put a breakpoint at the top of Lang , causing Eclipse to suspend the thread when the Lang class is loaded. This breakpoint is hit while the

I'm using Spring AspectJ for logging method execution statistics, however, I want to exclude some classes and methods from this without changing the pointcut expression. To exclude certain methods I created a custom annotation which I use to filter out. However I'm unable to do the same with classes. Here is my aspect definition - @Around("execution(* com.foo.bar.web.controller.*.*(..)) " + "&& !@annotation(com.foo.bar.util.NoLogging)") public Object log(ProceedingJoinPoint proceedingJoinPoint) throws Throwable { // logging logic here } NoLogging is my custom annotation for excluding methods.

I ams using Spring 2.5.6, asm 1.5.3, aspectjrt/aspectjweaver 1.6.1, cglib 2.1_3 In my Web based Spring application I have following class: package uk.co.txttools.aspects; @Aspect public class LoggingAspect { @Before("execution(* uk.co.txttools.web.controller.compose.PreviewMessageController.set*(..))") public void setLoggingAdvice(){ System.out.println("********************************* Advice run..... set mothod called...."); } @AfterThrowing("execution(* uk.co.txttools.web.controller.compose.PreviewMessageController.onSubmit(..) throws java.lang.Exception)") public void hadleException(){

I know the standard way of writing an AOP advice around a controller method and that you can get access to the HttpServletRequest arg, if declared in controller method. But my scenario is that I have a translation service, that is currently session-scoped maintaining the user's locale for translation. I feel this makes the service stateful and also I do not want it to be session-scoped, as I think it is really Singleton. But there are multiple places where the translation service methods are called and so I do not want to change the signature to add request/locale in these methods. The problem

From Spring Documentation : any join point (method execution only in Spring AOP) where the proxy implements the AccountService interface: this(com.xyz.service.AccountService) any join point (method execution only in Spring AOP) where the target object implements the AccountService interface: target(com.xyz.service.AccountService) I don't understand what "target object" and the expression target(...) mean. How is target different from this ? this(AType) means all join points where this instanceof AType is true. So this means that in your case once the call reaches any method of AccountService

I've seen that a few instances of this problem have been raised already. However, I am confident that I satisfy the criteria that has been outlined in those solutions. i.e. I'm pretty sure I have the desired jars on my class path + my schemalocation addresses look in order. One solution mentioned that the issue can be caused by having another XML parser on the classpath. I do have dom4j on my classpath but I have removed it to test, and the problem persists. Here's my classpath: <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="src" path="src"/> <classpathentry kind="src

Spring docs say: After advice must be prepared to handle both normal and exception return conditions. @After("com.xyz.myapp.SystemArchitecture.dataAccessOperation()") public void doReleaseLock() { // ... } I'm interested in knowing whether dataAccessOperation completed normally or with an exception. Unfortunately, the above code snippet is in the run for the most useless documentation ever produced. I understand that I can use AfterReturning and AfterThrowing separately, or even Around , but that's not the point. Since After exists, I should be able to use it. What the documentation wants to