I know, that’s a honey of a title, but you found this didn’t you?
Anyways, after some house cleaning and re-organizing of the projects that make up RightsPro in Eclipse I found that domain objects annotated with Spring’s
@Configurable annotation were no longer having their dependencies injected when running the app in tomcat or when running
AbstractTransactionalDataSourceSpringContextTests unit tests.
Turns out I must have removed the AspectJ library during re-organization and added it back in which also seemed to wipe out the AspectJ Build settings in the project properties. When AspectJ does its compile-time weaving it doesn’t know anything about the
@Configurable annotation unless you add spring-aspects.jar to the Aspect Path tab in the AspectJ Build settings.
F yeah, magical aspects are back in business.