Link Details

Link 502483 thumbnail
User 95751 avatar

By pt93903
Published: Oct 17 2010 / 11:56

I do have some issues with Cameron's statements that frameworks are mistakes of the J2EE past and that Java EE 6 represents the future. Open source frameworks made J2EE successful. Struts and Hibernate came out in the early days of J2EE and still exist today. Spring came out shortly after and has turned into the do-everything J2EE implementation it was trying to fix. Java EE 6 might be a better foundation to build upon, but it's certainly not going to replace frameworks.
  • 70
  • 2
  • 7242
  • 57


Add your comment
User 457955 avatar

Alexander Orlov replied ago:

-1 votes Vote down Vote up Reply

Nothing replaces something over-night. But there are directions of tech evolution. No doubt, Spring will also be wide-spread in 5 years. However JavaEE 6 is the modern and emerging technology of the present which may supersede Spring as the primary framework for enterprise projects in the long-term.

User 393686 avatar

RawThinkTank replied ago:

0 votes Vote down Vote up Reply

Those who dont go for POJO live in dark ages for rest of their lives unable to understand whats wrong with them

User 447031 avatar

iirekm replied ago:

0 votes Vote down Vote up Reply

Spring still has much, much more features than JEE. Hibernate still has more features than even JPA 2. There are better ways to create GUIs than JSF or JSP (parts of JEE standard). What's more people still think of JEE in terms of dirtiness of EJB 2.
For these reasons of productivity JEE 6 won't replace Spring+Hibernate tandem in next years, but JEE 6's popularity will probably grow. Probably the only truly standard part of JEE is Servlet API - which Java web framework doesn't use it at the bottom?

User 199388 avatar

glamdring replied ago:

0 votes Vote down Vote up Reply

I wouldn't agree fremeworks like spring will be obsoleted as well. Here is my extended opinion:

User 215370 avatar

rainwebs replied ago:

0 votes Vote down Vote up Reply

It is still the same discussion about "we are late, but we are the JCP standard, and because of this better" and "the ugly industry standard stack that everybody uses for years (all frameworks we love)". Matt did a good job on describing why there is no change in this race, even with JEE 6. I do not expect any change within the next years. Why should someone using Spring for years port to a standard that nobody needs anymore. If we had all this discussion before Spring was invented, maybe this had helped a bit.

Would be nice if a bit more of those JCP investments would be used to get a better Web container architecture. The JSF critics Matt mentions shows that the problems are in the frontend technologies. Although I am one of those JSF "book" promoters, I have to agree on this ;-).

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Written by: Bert Belder
Featured Refcardz: Top Refcardz:
  1. Design Patterns
  2. OO JS
  3. Cont. Delivery
  4. Java EE7
  5. HTML5 Mobile
  1. Debugging JavaScript
  2. OO JS
  3. JSON
  4. Ajax
  5. REST