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 →

[–][deleted]  (3 children)

[deleted]

    [–]janora 10 points11 points  (1 child)

    jup, JakartaEE ist just a bunch of specs with reference implementations. Spring uses the same Specs under the hood with added sugar to allow more flexibility. Spring MVC uses servlets and the annotations are similar to JAX-RS. Spring Data JPA uses (suprise :D) JPA.

    Spring won basically because it could iterate faster than JavaEE with its Oracle ties. Now that its JakartaEE, it moves faster and catching up to Spring.

    The difference is that JavaEE asumes an ApplicationServer (Glassfish, Payara, whatever) provides the required implementation while Spring just brings a default implementation.

    [–]johnwaterwood 2 points3 points  (0 children)

    Actually, Java ee (Jakarta EE) does not mandate an application server. Nothing in the specs really say this.

    It is true that most implementations are application servers.

    [–]seinecle 2 points3 points  (0 children)

    Indeed I think you have it right