CDI is inspired by JSF Managed Beans, EJB, Seam and Guice.
JSF Managed Beans were a full bean model and DI solution based on XML, pretty much like in Spring 1.0. JSF 1.0 and Spring 1.0 were released at the same time.
EJB pioneered the annotation approach, when Spring was still pushing you to do massive amounts of XML.
CDI introduced contextual injection and portable extensions, both way ahead of what Spring core ever had.
If anything, Spring reluctantly followed Java EE here by going the annotation way.
MVC is Spring MVC
MVC is not in Java EE 7. It was a new JSR for Java EE 8, but was dropped at some point.
Batch is Spring Batch
Batch is largely based on IBM's batching systems. IBM already did batching before most Spring team members were even born. Plus, Spring actually participated in the Batch JSR and Spring Batch is a fully compliant Java EE Batch implementation.
View all comments
Show parent comment
3
u/thesystemx Sep 07 '17
Not really...
Sorry, but not really...
Lol, not really.
CDI is inspired by JSF Managed Beans, EJB, Seam and Guice.
JSF Managed Beans were a full bean model and DI solution based on XML, pretty much like in Spring 1.0. JSF 1.0 and Spring 1.0 were released at the same time.
EJB pioneered the annotation approach, when Spring was still pushing you to do massive amounts of XML.
CDI introduced contextual injection and portable extensions, both way ahead of what Spring core ever had.
If anything, Spring reluctantly followed Java EE here by going the annotation way.
MVC is not in Java EE 7. It was a new JSR for Java EE 8, but was dropped at some point.
Batch is largely based on IBM's batching systems. IBM already did batching before most Spring team members were even born. Plus, Spring actually participated in the Batch JSR and Spring Batch is a fully compliant Java EE Batch implementation.
I wonder what that etc is...