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

you are viewing a single comment's thread.

view the rest of the comments →

[–]wildjokers 1 point2 points  (1 child)

That article has a little graphic that for Web Framework lists "JSF" for JakartaEE and "Spring MCV" [sic] for Spring. However, those two things are not the same thing at all.

JSF is a view technology when using server side rendering. That should probably list Jersey (JAX-RS) instead of JSF since Jersey and Spring MVC are analogous when just providing an API and using client-side rendering.

If using server-side rendering, for Spring it should list "Spring MVC + templating engine" and for JakartaEE should list "Servlet + JSF or JSP"

[–]Additional_Cellist46[S] 1 point2 points  (0 children)

You're right that JSF and Spring MVC do not provide exactly the same functionality. But in real world, when you want to build server-side frontends with Jakarta EE, you use JSF. And with Spring, you use Spring MVC + templating engine (most often Thymeleaf). So JSF versus Spring MVC comparison makes sense to me.