J2EE Development without Spring
Friday, September 26th, 2008 | Author: FoX
Spring Source has changed its maintenance policy (press release). From now on we’ll have to buy commercial support for maintenance releases of the Spring framework if we still want support after 3 months. This worries me a lot as Spring was becoming the defacto standard in J2EE development.
The need for a new book on Java EE is rising and I already got a perfect title for it! How would “J2EE Development without Spring” sound like? The cover 
:
This book would explain how you could still be agile in your development environments, without breaking your codebase and how you can get around the problems Spring currently has: too bloated, a lot of functionality and a lot of ways to get something done (annotations, various xml configs to do the same).
After the venture capitalists came into the picture, the company isn’t managed anymore by ambitious developers who want to make the J2EE world a happier place. In fact, as Rod Johnson will still be the CEO, a new COO was appointed and clearly states that it is controlled by the Venture Capitalists now! Spring Source has to realize that the community made the Spring framework by embracing it into their development environments, contributing and helping each other around. This gives them also the power to break it again, as there are alternatives that provide the foundational principles of Spring (Guice anyone?). And as Spring doesn’t have an invasive model, it is quite easy, and thus not unimaginable, that a massive switch will take place.
The community currently has a lot of questions regarding this change. Let’s take the 2.5 release as an example. If the policy would apply to this release, the community can only use Spring until version 2.5.1. We would have to pay a lot ($ 22.500 in the case of Ryan de Laplante) if we would like to profit from release 2.5.2 till 2.5.5 (and newer).
A lot of things are unclear at the moment and how Spring will evoluate in the future. Maybe this is an ideal change for the community to profit from their experience and start all over again? There is also a possiblity that the community will start its own Spring Community track. What will be the case and what will be best for the community and J2EE in general?
Friday, 26. September 2008
Great idea. When do you start writing?
Friday, 26. September 2008
I would like to see this book! Spring is KAPUT!
Friday, 26. September 2008
I think there’s some misconception on the Spring “debacle”. “Support” was already a premium expense. They won’t be providing precompiled binaries for 3 months after maintenance releases.. But the source will be made available, and can be built.
Friday, 26. September 2008
JEE not J2EE
Friday, 26. September 2008
Excellent. Spring is way overrated anyway.
Friday, 26. September 2008
Bryce: as there will be no tags, you can’t be sure you are building a stable release.
Mark: I know, but the cover is a parody which stated it as J2EE. Besides that, J2EE sounds much cooler than JEE
Friday, 26. September 2008
Are you kidding? Neither J2EE or JEE sounds cooler.
Django’s the shit.
Friday, 26. September 2008
Actually, it’s neither J2EE nor JEE but Java EE. See the explanation at the bottom of the page found at http://java.sun.com/javaee/.
Friday, 26. September 2008
this book is actually a good idea.
Saturday, 27. September 2008
Spring is just an alternative. Now with the new support plot, it just stinks.
Saturday, 27. September 2008
I will add this book to my collections.
Monday, 29. September 2008
I hate frameworks…they have really put off programming in Java…as every job or company I worked for had their own favourite. I stopped programming in J2EE/JEE or Java EE…whatever they call these days over two years ago…and I don’t miss it. Now program in ASP.NET C#, and PHP.
Tuesday, 30. September 2008
Have you read this: http://www.springsource.com/products/enterprise/maintenancepolicy/faq ?
Tuesday, 30. September 2008
I’ve read the FAQ, but that doesn’t change anything to this statement. As all source code should be publicly available, what about the source of Spring 3.0?
Wednesday, 1. October 2008
We can put a subtitle to new framework… Summer! Open source is a strategy to make money. No doubt it’s a symbiosis system but still giant keep their one lag in the loop to stay with the market. Its a cheap way to avoid big budget on research and avoid mishaps for large investment.
Wednesday, 1. October 2008
Nice IDEA!!!!
You got my vote!!!