- "Many" was jumping onto the Spring framework. My sole answer to this was that one day Java EE framework will be matured and there is no need to download MBs of jars to make a simple application.
- Certification, certification, certification: Don't you just hate it when a new product is out on the market and you need to get yourself certified to be known as an expert of that product? There are various frameworks out there that can do the same functionality as the other, so it's a matter of taste and preference. (You may ask, am I Java certified? Not yet!).
- Jack of all trade: I am always told that Spring does "everything". Generally, I have yet to see an application that uses every feature of Spring.
I am not shooting down Spring framework, in fact I have used it myself and I use it due to its simplicity in getting written code to run (i.e, you see productive results in quicker time than when using Java EE API's). This can be greatly attributed to Spring template helper classes and very (if not no) configuration required. The problem I had was that my simple web app was over 13MBs bundled WAR file because of various Spring dependencies jars. Also, I was one of the rebellious people who said that Java EE will mature and when it'll mature, I will be amongst the first to embrace it and move on. Now, I can tell you that my current web application (which has no dependencies on any Apache modules, Spring modules, etc. and just pure Java EE API's) is less than 6MB's WAR file. The other are web frameworks bundled such as Twitter Bootstrap 3.x, Font-Awesome, WooThemes FlexSlider, etc. (it'll soon be replaced by it's CDN URL, so the size of the WAR file will drop).
To understand what I mean, see the Fifty Features of Java EE 7 in 50 minutes.
Heck, Oracle tried to convert the Spring developers to Java EE by convincing them that Java EE is no longer "Java Evil Edition".
Will Spring framework die? I am not sure, in fact, they've aligned their framework to work with Java EE API's. Red Hat had a framework called Seam Framework and they halted its development on Seam3. I used it as well, and I liked it. The Seam team decided to take on a different approach and "merge" themselves with other CDI developers out there to form Apache Deltaspike. And no, it seems Seam won't die.
Back to Java EE maturity, by running your enterprise application on a Java EE 7 compliant container, you certainly won't be worrying of dependencies. Configurations are there, in some cases (e.g., setting up Resources such as Mail Session, JDBC Datasources, etc.) but I have seen that it's very minimal.
Yes, Java EE is now mature to compete with the likes of Spring framework & I believe that we can write a full enterprise application by simply using Java EE API's. In fact, I have already started.
What are your thoughts? Let me know in the comment below.