{"id":1482,"date":"2012-07-25T19:00:00","date_gmt":"2012-07-25T19:00:00","guid":{"rendered":"http:\/\/www.javacodegeeks.com\/2012\/10\/java-ee-6-vs-spring-3-java-ee-has-killed-spring-no-way.html"},"modified":"2012-10-22T05:52:48","modified_gmt":"2012-10-22T05:52:48","slug":"java-ee-6-vs-spring-3-java-ee-has","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2012\/07\/java-ee-6-vs-spring-3-java-ee-has.html","title":{"rendered":"Java EE 6 VS Spring 3 : Java EE has killed Spring? No way!"},"content":{"rendered":"
Introduction<\/strong><\/p>\n

Few days ago, I was listening to the epsiode 85 of the Java Spotlight Podcast<\/a>. In this epsiode, Bert Ertman<\/a> and Paul Bakker<\/a> were talking about migrating from Spring to Java EE. Basically, in their introduction they were saying that, nowaday, there is no point choosing Spring over Java EE. We can read in their article : <\/p>\n

It took a while but Java EE has finally made the leap to be a standard, lightweight, fitting solutions to the vast majority of real-world development challenges in the mainstream enterprise applications space. You should have no single reason beyond choosing the standard. <\/i><\/p>\n

Over the last couple of months, I have seen a lot of blog articles with similar thoughts. Some are praisising Java EE, which is a good thing, while others are just denigrating Spring. This is the case of the article<\/a> of Arun Gupta. My first thought on this article was \u201cOracle might be really desperate to write such trolls\u2026\u201d. <\/p>\n

I am not at all a Spring evangelist nor a Java EE hater. At the contrary, I have used intensively Java EE 5 for 2 years and am really happy to see that Java EE finally became a good competitor for Spring. My goal is not to praise Spring here, just to balance the words of the \u201cSpring\u2019s hater\u201d. <\/p>\n

Standard VS Single vendor solution<\/strong><\/p>\n

Is that good to have standards? <\/p>\n

Do you know this sentence \u201cResponding to change over following a plan\u201d? Yes, it is one the Agile rules. Of course it is a good thing to have standards, it is more than good, it is fundamental! But it comes with its drawbacks. If one day you have a problem with the standard, something not covered by the standard, your only solution is to fill an issue, cross your finger and wait 3 years\u2026

<\/div> <\/div><\/p>\n

Are Spring and standards incompatible?<\/strong><\/p>\n

Not at all! That is one of the reason I do not understand the \u201cIt is standard\u201d argument. Spring does its best to provide the use of the standard. You are free to use JPA, the CDI annotation etc. I consider Spring more like an integration platform that let you use all Java EE technologies and also some additional features provided by Spring itself. <\/p>\n

Do I depend on SpringSource? Not really\u2026<\/strong><\/p>\n

What happen if tomorrow SpringSource stop developing Spring? I will continue using it\u2026 Spring Framework is under Apache 2.0 license, no doubt that the community will take the relay and that some new companies will offer support for Spring. Even if nobody do that, I am happy with Spring Framework in its current state, why would I change? Maybe I will reconsider it in 3 years, when a new version of Java EE will be released\u2026 <\/p>\n

What happen if tomorrow I am not happy with Spring Framework? The same thing than if I am not happy with Java EE\u2026 I stop using it\u2026 <\/p>\n

What happen if tomorrow I am not happy with my application server? The same thing than if I am not happy with Java EE\u2026 I change it\u2026 Except that, with Spring, I will have more choices (since Spring works with all Java EE application server + the others like tomcat, jetty etc\u2026). <\/p>\n

Spring has always been innovative and will always be<\/strong><\/p>\n

I will never forget that Spring has made CDI possible and easy for the Java web development. Java EE has followed (again 3 years later\u2026) with the JSR-299<\/a>. <\/p>\n

Spring is also currently providing some awesome solutions not provided at all by JavaEE:<\/p>\n