4 ms·

# 3. Java EE is legacy tech. While deeply entrenched, most of the work out there for it today consists of maintenance or migration to more service-friendly appr

by mohaine 10y ago

# 3. Java EE is legacy tech. While deeply entrenched, most of the work out there for it today consists of maintenance or migration to more service-friendly approaches like Spring or Dropwizard. 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.

specialist 10y ago
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.
- geodel 10y ago
  Thank you. Maybe you don't know but you have given very apt description of Java land frameworks.
- mohaine 10y ago
  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.
pieterh_pvtl 10y ago
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".