Lately Oracle is providing a podium for people (you know who you are) who are telling you that you should migrate from Spring to Java EE. The first articles making that case started appearing a year and half or so ago but it seems Oracle isn’t giving up. They should, because the case their minions are making on their behalf is so flawed that it’s an insult to common developer sense. I’m not making the case that Spring is better (that would be a different article), I just want to point out that you have nothing to gain from performing the migration they are proposing.
The article that accompanies the podcast episode starts out spreading some FUD about Springsource / VMware as being not trustworthy. I think Vmware are as reliable as any other company, and certainly not less reliable than Oracle or any of the other application server vendors out there. Jumping ship to another vendor will not improve your situation in that regard.
The authors try to frame Springsource as not caring about standards. I would say that they do care about standards, just not the way Oracle wants them to. Observers of the Java ecosystem know that Oracle has been offending people left and right. Springsource took active part in JSR 330, on dependency injection. Springsource, like others, just isn’t asking ‘how high?’ when Oracle tells them to jump. The Java Community Process has been having problems for quite a while now. It has been like a political party that is fighting within. Voters will leave them en masse. In general, any standard must also be the de-facto standard, or it is worthless. If a de-facto standard is not approved by some standards body, that is a testament as to how well the standards body is functioning.
Then, the authors argue that Java EE is more lightweight than the Spring portfolio because the size of a warfile can be kept smaller. They leave out the part where you then have to deploy into a Java EE appserver which is as heavyweight as it gets. So you’re exchanging ‘big war file’ for ‘big app server’, hardly a win.
After that the article mumbles on about how Java EE 6 can now also do some of the things Spring Framework has been providing for god-knows-how-long, such as AOP and an integration testing framework. I suspect you are as unimpressed by this as I am.
I’m left here wondering why seasoned developers would voice this opinion so actively. By now I’m sure they know very well when it is worth doing a big migration from Tomcat to a Java EE appserver. The case they’re making for it is unconvincing, and they know it.