Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Let us say Java didn’t have annotations. What would be the ideas you would come up with to design something like Google Guice’s DI framework? I am fairly new to Java and cannot think of anything other than
How would you inspect the elements that needed to be injected? What would be your ideal way of configuration other than annotations?
The popular Plexus IoC(similar to Spring) uses Commons Attributes to provide annotations like metadata via special javadoc comments. This allows it the ability to work on older JVM(pre 1.5 that didn’t support annotations while still reaping some of their benefits).
Btw JUnit 3 had nothing like this – it simply enforced a naming scheme for the tests – each test method had to be named “testSomething” so that it would recognized as a test and executed by JUnit. This is technique commonly referred as “convention over configuration“.