Hi, Do you get a warning when LTW that a type is not exposed to the weaver? (the top most one) Given the description that it is behaving when being built as an eclipse project, that suggests the aop.xml configuring the LTW has a problem.
What version of AspectJ LTW are you using? If you are on 1.6.7 then you may have issues if you are using certain include/exclude clauses in the aop.xml. I would recommend moving off it onto 1.6.8 or 1.6.9. If you give me more details on the aop.xml, maybe we can work out whats up. cheers, Andy On 16 August 2010 04:29, Shashikant Kale <[email protected]> wrote: > Hi, > > > > I have been using aspects for some time in our application. I had few unit > test cases for a cross cutting functionality of auditing data changes on JPA > entities. This was done using LTW. However now when I try to run the unit > test case within eclipse, I am facing a strange issue of top level entity > not getting weaved. However the entities which are child level are getting > weaved. I found this by enabling showWeaveInfo flag in the aop.xml. > > > > When I try to switch to AspectJ development perspective in eclipse, it shows > that the methods of the parent entity also are weaved. However in the LTW > doesn’t really weave the code. > > > > I am not sure what the reason could be for this strange behavior. Could > somebody please throw some light? > > > > Regards, > Shashi > > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
