Frameworks like Spring have ridden the IOC / dependency injection wave to popularity. However with Java EE 5.0 and EJB 3.0, dependency injection capabilities will be very much part of Java EE.
Debu Panda in his article “Using Dependency Injection in Java EE 5.0” says that “Dependency injection (in Java EE) is the inverse of JNDI. It lets you declare dependencies and lets the Java EE container handle the complexities of service or resource instantiation and initialization when the resource is required.”
In Java EE 5, you can easily use dependency injection for resources, datasources and even web services. A few vendors already have released EJB 3.0 ready servers. So the question is “Is the dependency injection framework wave over and should you now look only at Java EE for your dependency injection needs?”
>> How to decide which persistence technology to use? JDBC / CMP / EJB / Hibernate?
>> With EJB 3.0, any Java developer is an EJB developer
>> What’s special in EJB 3.0?
>> 5 good things about the Spring framework
>> Checking EJB 3.0 performance
>> Spring In Action: 9I Book Review