By dev.stonez
via kai-waehner.de
Published: Nov 22 2011 / 07:51
Why I will use Java EE (JEE, and not J2EE) instead of Spring in new Enterprise Java Projects in 2012
The question comes up often. It came up in my new project in November 2011, too. I will use Java EE (JEE) instead of the Spring framework in this new Enterprise Java project.
I know: Several articles, blogs and forum discussions are available regarding this topic. Why is there a need for one more? Because many blogs talk about older versions of Java EE or because they are not neutral (I hope to be neutral). And because many people still think thank EJBs are heavy! And because the time has changed: It is Java EE 6 time now, J2EE is dead. Finally! Finally, because not only JEE 6 is available, but also several application servers (not just Glassfish as reference implementation). I do not want to start a flame war (too many exist already), I just want to describe my personal opinion of the JEE vs. Spring „fight“…
-
C++ exceptions under the hood
-
Zoom Image Demo In Android | Zoom Image Example with code in Android | MotionEvent, Matrix example in Android
-
Visual Studio 2012 Support is Added for Aspose .NET & SSRS Components
-
Writing Testable JavaScript
-
The Great Java Application Server Debate with Tomcat, JBoss, GlassFish, Jetty and Liberty Profile
-
Why I left Heroku, and notes on my new AWS setup
Comments
Miloskov replied ago:
I was using Java EE 6 for a project and Its easy and awesome but Im still going back to Spring. Spring always is on the edge and I like that, JavaEE always seems to catch up Spring.
JCP/JSR is a very slow process, Open Source and Agile beats bureaucracy.
Voters For This Link (25)
Voters Against This Link (9)