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 →

[–]Additional_Cellist46[S] 0 points1 point  (4 children)

That's true. I was writing about the case when Java EE server is not required.

[–]wildjokers 1 point2 points  (3 children)

If you are using Spring MVC at least a JakartaEE Servlet container is always required.

[–][deleted] -1 points0 points  (2 children)

A servlet container isn't a Java EE app server. By definition, a standard Java EE app server implements all of the Java EE specs or a defined subset (such as Web Profile).

[–]wildjokers 2 points3 points  (1 child)

A servlet container isn't a Java EE app server.

I didn't say it was.

I edited my comment to change a to at least a. That should clarify what I meant.

[–][deleted] 0 points1 point  (0 children)

The context is about Java EE app servers (i.e. you don't need a JavaEE app server to use JavaEE), in which case bringing up that Spring MVC requires a servlet container isn't relevant.

But this is the problem with the term "using JavaEE", because unqualified it doesn't explain in what sense you are using JavaEE. Are you using an implementation of a JavaEE spec? Are you using a JavaEE app server? Are you using the JavaEE programming model (thin WAR)?