• JEE applications still contain excessive amounts of "plumbing" code
• Abusive distributed object model in many JEE applications are conceptually wrong
• The EJB component model is unduly complex
• EJB is overworked and overpaid
• JEE Design Patterns are not design patterns, but workarounds to compensate technology limitations
• Hard to unit test for JEE applications
• Certain JEE technologies have simply failed. The main offender here is entity beans
Embedded Link
Wrox Article:Why Use the Spring Framework? – Wrox
The Spring Framework is an open source application framework that aims to make J2EE development easier. Unlike single-tier frameworks, such as Struts or Hibernate, Spring aims to help structure whole …
what amused me was once upon a time was when I found out that some folks at SUN did a strong critique of "distributed objects"… before (!!) SUN came up with EJBs !!
I can't find that exact report right now, but I think this wikipedia entry refers to the same thing:
http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing
what amused me was once upon a time was when I found out that some folks at SUN did a strong critique of "distributed objects"… before (!!) SUN came up with EJBs !!
I can't find that exact report right now, but I think this wikipedia entry refers to the same thing:
http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing