JavaOne 2011: Migrating Spring Applications to Java EE 6
by ertmanb on Oct 09, 2011
- 28,836 views
The Spring Framework has no-doubt played a major role in evolving the way we write enterprise applications on the Java platform today. However, it is still a proprietary framework owned by a single ...
The Spring Framework has no-doubt played a major role in evolving the way we write enterprise applications on the Java platform today. However, it is still a proprietary framework owned by a single company. The age of having to rely on such proprietary frameworks in order to develop decent enterprise applications is now over and Java EE 6 has become an even easier way to develop enterprise applications based on standards which makes it the best choice for any enterprise application. In this session you will experience how to migrate a typical full stack Spring application to a standards based, completely portable, Java EE 6 application including integration tests.
Accessibility
Categories
Upload Details
Uploaded via SlideShare as Adobe PDF
Usage Rights
© All Rights Reserved
Statistics
- Likes
- 40
- Downloads
- 924
- Comments
- 8
- Embed Views
- Views on SlideShare
- 25,414
- Total Views
- 28,836
Indeed CDI is great. And have good design elements.
Anyway EE worries me.
A container? my freedom? Why cant I run my application in a main program?
That is where Spring is great.
Spring does not tell me to run in container X.Y.Z ...
I can run my applications in a unit test. Limit the IOC to what I need in a situation.
But in EE6 I cannot !!!!
If JSR-330 was jsr-330.jar - I would be happy. But it is not. Therefore I think that the whole idea of containers implementing a stack EE6 is bad from the beginning of.
At the end of the day JSR-330 and all the other specs loose meaning. The only meaning is EE it self. Or to be more precise the vendor that I got started with Jboss, Weblogic, Glassfish, Websphere sets the limit for my application. Not me any longer.
I loose control I loose freedom.
Give me my freedom back. Give me the freedom to run main() 1 year ago
http://agoncal.wordpress.com/2011/10/20/o-java-ee-6-application-servers-where-art-thou/
Signed, Pieter (Oracle Employee) 1 year ago
>No matter how many fancy slides you show us, even Java EE 6 is no match for Spring...
Care to explain why? 1 year ago
no matter how many fancy slides you show us ... even jee6(0) also no match for spring... 1 year ago
It’s almost always not technically a pain, but it’s a cultural kind of pain. There is some system administrator group or high-level architect who puts this policy in place that ’the server may not be upgraded’.
>If JEE adds the option of embeding the ’JEE container’ in the application (Thus running a JEE7 ear on a JEE5 or JEE4 appserver)
It shouldn’t be technically necessary, but politically... this would be a HUGE move for Java EE. I think it might even be a game-changer. Have e.g. a JBoss AS 7 embedded inside a WAR, that would only be bootstrapped by the lowest of the lowly Servlet containers out there (e.g. Tomcat 4 or 5 orso?) and then completely take over.
Let Tomcat be the BIOS, and let Java EE be the OS. 1 year ago
Starting with EE 5 and certainly with EE 6 there is no need to go outside of the Java EE specification to accomplish what could easily be done by using pure Java EE. And if EE 7 will get the cloud based hosting right, I think it will be really hard to make an argument for using Spring. 1 year ago
The key thing on this topic:
What percentage of the big companies have a J2SE 1.5 V2.4 or higher servlet container?
What percentage of the big companies have a JEE6 complaint application server?
The biggest problem of JEE is the dependency on an application server. For most big companies upgrading an application server is a big pain. Many big companies still run their appications on a J2EE 1.4 application server.
If JEE adds the option of embeding the 'JEE container' in the application (Thus running a JEE7 ear on a JEE5 or JEE4 appserver), it would be a lot more usable and less risky to go for JEE. The 'write once run everywhere' argument for Spring would still make me choose for Spring for most situations / environments. 1 year ago