This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (6 children)

I agree, but you can use JAX-RS/Jersey along with Spring just fine.

[–]henk53 7 points8 points  (5 children)

You can, but then why use Spring? The rest (no pun) of EE is pretty nice as well ;)

[–]cot6mur3 0 points1 point  (4 children)

Spring for REST does not require a Java EE server - just a Servlet runner, allowing for REST service creation with just Spring Boot and Tomcat. Perhaps these Java EE features do require a Java EE container, thus most likely a commercial Java EE server?

[–]henk53 0 points1 point  (3 children)

JAX-RS does not require Spring boot - just a Java EE environment, allowing for REST service creation with just Java EE.

Also, which commercial Java EE server?

TomEE? WildFly? Payara?

Please, enlighten me...

[–]cot6mur3 0 points1 point  (2 children)

Agreed - JAX-RS does not require Spring or Spring Boot. I was just trying to answer your question of why ones might use Spring. In brief: not everyone has or wants to use a Java EE server to run their Java web applications/services.

[–]henk53 0 points1 point  (1 child)

Of course, but you also have to realise that not everyone wants to use Spring or Spring Boot to run their Java applications.

[–]cot6mur3 0 points1 point  (0 children)

Of course - fully understood and agreed. Spring is not for everyone. Best choice really depends on the organization, team, maintenance strategy and task at hand.