Re:Oracle and the fall of Java EE
by specialist on Friday July 08, 2016 @09:55AM
(#12055465)
Java EE is just a collection of libraries. JMS, JNDI, etc.
Said mostly in humor (from long suffering):
The distinction between J2EE and Spring is pretty simple. EJB is a data persistence obfuscation library, whereas Spring's DI/IoC "framework" is an exception (stack trace) obfuscation library.
The distinction isn't very clear. As you say J2ee is just a collection of libraries, of which Spring web services happen to use a subset of.Servlets/JAX-RS off the top of my head.
Of course Spring doesn't leverage ALL of J2ee but I wouldn't except anything to use all J2ee. There is a lot there.
Thank you. Maybe you don't know but you have given very apt description of Java land frameworks.
Re:Oracle and the fall of Java EE
by pieterh_pvtl on Friday July 08, 2016 @03:13PM
(#12057932)
I wouldn't say it's Java EE based, acutally. It's a superset of Java EE. It's wraps the APIs people still actually care about like JPA, Servlet, and works with JAX-RS. The rest of the Java EE APIs are pretty much irrelevant these days, as evidenced by the constant introduction of new "profiles".
While I mostly agree with you, Spring _IS_ J2ee based. (i.e. Servlets/JAX-RS both part of J2ee). Sure it doesn't use EJB but I don't think anybody does (non legacy) at this point.