java - Spring AOP - why do i need aspectjweaver? -


I have written a very simple aspect with Spring AOP, it works, but I have some problems that are actually going on Are there. I do not understand why I have to add aspects? The Spring AOP document clearly states that unless I just use Spring-AOP, I do not need the ASTJ compiler or weaver:

AOP Runtime still pure spring AOP , And there is no dependency on the AspectJ compiler or weaver.

My configuration looks like this:

  & lt; Aop: aspectj-autoproxy / & gt; Check @ Aspect @ Service Public Class RemoteInvocation {@ prior ("execution (* at.test.mypackage. *. * (..))" public void test () {System.out.println ("test") ; } ...   

I also tried XML configuration, however nothing changed. Maybe I'll let it go, but I really want to understand why the aspect-weaver is used? If I do not add dependency in Maven, then I get java.lang.ClassNotFoundException: org.aspectj.weaver.reflect.ReflectionWorld $ ReflectionWorldException

Spring AOP implementation I think some sections are being reused from the aspects-weaver. It still uses the dynamic proxy - the byte code does not modify.

The following explanation can be given from the Spring Forum.

The case is not using Aspecz Weaver in this spring. It is only reusing some sections from the facets.

- Ramanwish

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -