Let's see if G+ works better for this than twitter does. I'm not going to write a blog-post about it. But I feel the need to say a little bit more than 140 char about it ;)

I finally stumbled upon +Arun Gupta (https://blogs.oracle.com/arungupta/entry/why_java_ee_6_is) and +James Bayer (http://www.iamjambay.com/2012/03/arun-gupta-java-ee-6-and-spring.html) s posts about #JavaEE6 vs #Spring . And even +Antonio Goncalves jumped in with some comments about it (http://www.iamjambay.com/2012/03/arun-gupta-java-ee-6-and-spring.html?showComment=1332498601350#c3911241791435466937).

I'm an Java EE advocate since years now. And even I had to work with #Spring and a lot of it's components. There have been times when it was a true lightweight pleasure to use what former springsource team had to offer. Especially if you were into MDD or stuff like that quite early. The whole problem I have seen with customers using one or the other is that they mad a decision about this. And started defending it over and over again. For years. Until today. No matter which arguments were standing in the room. With spring starting to offer non-standards compliant solutions for problems the standards had back in the days some companies missed to jump back on the standards train at all. And they are paying for that. The one or the other way. Maybe by not being able to attract young developers. Maybe by having to wait for a solution. Maybe by no longer being able to use or integrate with upcoming standards. Maybe by something else. Maybe I missed something here.
It's obvious less risky to have a first class ticket on a standards-driven train. But it was expensive until #JavaEE6 came up. Why? Because you had to take the long road on some things. You had to implement a lot. You had to cope with shortcomings and with some older standards you also had to commit yourself to a vendor (CMP). So to me it seems as if sticking to the JavaEE standard just started to pay back to those sitting there since the beginning. And to me it feels as if this train only recently started to gain speed again. Without having looked into the separate features and components I have the feeling that from a technology point of view the break even for using the JavaEE standard in favor of spring has come.

As a consultant I have to look at the customer first. So, depending on the shop the customer is in, I have to choose which way to go. If someone is asking me what to do I would propose a broadly adapted standard. As of today. For enterprise grade #Java this clearly is Java EE.

Some (personal) last sentences to +Arun Gupta and +James Bayer :
I thankfully know both of you. You have been on the same company for quite some time working in the same field. I don't know if I like to see what's happening via your blog-posts at the moment. You should sit together and work out a common view on both platforms and start offering a real decision matrix. Step back from positions and start offering solutions. Anybody skilled enough to work with any of the two platforms knows about this "ancient fight" and has his positions here. So you both are targeting the young ones, the greenhorn developers with this discussion. And you should, no you have to, make this a valuable discussion.
But those are only my 2 cent.
Shared publiclyView activity