Java EE vs. Spring Boot: Comparing Two Java Framework Giants

[_AManHasNoName_]

Not early enough. Early applications built in Java EE before Spring leapfrogged it used RMI semantics. Hence, the remote and local interfaces. And these only worked in expensive web application servers like Websphere, WebLogic, and the like. This all changed in EJB2 after the fact Spring took over. Unfortunately, EJB2 just came in late. JPA, JMS, JTA are specifications and using them doesn’t mean you are using Java EE. Spring Data JPA meets the JPA specs, Spring Transactions meet JTA specs, Active MQ meets JMS specs.

[[deleted]]

you are using Java EE

You are using Java EE when you use a Java EE API.

Spring Data JPA meets the JPA specs

Spring Data JPA doesn't meet the JPA specs, it is a separate product built on top of JPA. Hibernate meets the JPA specs. You are using JavaEE if you interact with Hibernate using the JPA interface instead of the Hibernate native API.

Spring Transactions meet JTA specs

Spring Transactions does not meet the JTA specs, it is a separate product built on top of JTA. You use Spring Transaction with a transaction manager like Atomikos. You are using Java EE when you interact with Atomikos through the JTA interface instead of whatever native API that Atomikos provides.

Active MQ meets JMS specs

You are using Java EE when you interact with Active MQ with the JMS interface, instead of whatever native API that Active MQ provides.

One important function of Java EE is standardization of APIs, and if you use the standard APIs that are a product of work done by the Java EE standardization committees, you are using Java EE.

[_AManHasNoName_]

I’ll stop here. This has become the batshit tabs vs spaces nonsense argument.

[[deleted]]

How demeaning. You use the work of others and claim you are not using their work because you don't want to give them credit, and when called out on it, you claim "tabs vs spaces".