I have taken and exisitng and working eclipse/spring 2.56/xml configed application and migrated it to STS/Spring 3.0/Java Config application. Through this I have lost my ability to get my Junit4 test runing due to unsatified DI.
I have read the forums and all the blogs on this stuff - there is not that much out there.
The project compiles fine and my logs show it is finding the components (through the component-scan) but the junit test runs fails. I have a few tests that do not require DI (utils) and they test fine as they always have. but all DI based objects fail the @Required validation. This includes such infrastructure based DI like DataSource bean not found.
I am under no illusions that this is not a spring issue but some lack of or over configuration on my part. I have spent crazy amounts of time commenting things out, recreating the project in STS and copying source over and rebuilding confgurations - to no avail.
Any suggestions? This is driving me to drink and I usually like to walk to my drinks
The application config simply has Spring-annotations, tx annotation, LTW and component scan in it as well as a bean def for the main (and only) java config bean.
I can't believe it but I am thinking about learning Netbeans just to try some other path - this is not a threat just a result of my lack of ability to get past this
Thanks in advance for any support, Phill