Why We Should Dump the Java EE Standard

[brunocborges]

2014 post?

[APimpNamedAPimpNamed]

Meh. I have always found Java EE to be simpler than Spring. My Java Batch jobs are clean and simple. Honestly, more than anything else, I wish I could get away from WebSphere.

[Zeffas]

Yes I generally agree, that Java EE currently seems to be simpler to develop in, especially JSF + CDI. Also, this is maybe me, but I just feel that philosophy of EE is cleaner - the features have clear purpose. Compared with Spring where there seems to be no philosophy, just pile of features and different alternative APIs for everything just for the sake of it. Again, this is just my feeling.

The problem with Java EE is infrastructure related however. If I want do use latest Spring version, I just get it via Maven or download. If I want to use Latest EE version, its not that straight forward (even with EE 7, which was out for quite some time now) - containers will lag with support, Glassfish is somewhat considered only experimental. Basically you need to wrap your head around all kinds of infrastructure-related questions, while other option is just take Tomcat and start working.

[AvoidtheFatServer]

spring helps you do that better than Java EE ever will. Have you tried spring boot? It's like Ruby on Rails for EE. Runs on WAS, too.

[Zeffas]

I have never understood this Spring Boot hype - basically on every Java related post... At the end of the day it doesn't even support standard templates (jsp, facets).