I believe you are hitting a problem to do with types being loaded 'too soon' and thus they can't be setup correctly. The act of creating a new method in the test that specifies the type Entity will mean Entity is loaded much sooner than would be the case if it is just referenced inside a method. Using -verbose:class I could see that without the method it is loaded as about the 1300th class. With the reference it is loaded around 800.
I do recall a Spring Framework jira about this but I can't seem to find it. I'm not sure we actually solved it but we did document our findings - I don't remember if a workaround was described. cheers Andy On 14 July 2011 21:14, Setya <[email protected]> wrote: > Well, anybody, is this a known LTW limitation ? > > Setya > > -- > View this message in context: > http://aspectj.2085585.n4.nabble.com/Problem-Injecting-Dependencies-Into-Domain-Classes-Using-Configurable-AspectJ-tp3614021p3669190.html > Sent from the AspectJ - users mailing list archive at Nabble.com. > _______________________________________________ > 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
