📘 Premium Read: Access my best content on Medium member-only articles — deep dives into Java, Spring Boot, Microservices, backend architecture, interview preparation, career advice, and industry-standard best practices.
✅ Some premium posts are free to read — no account needed. Follow me on Medium to stay updated and support my writing.
🎓 Top 10 Udemy Courses (Huge Discount): Explore My Udemy Courses — Learn through real-time, project-based development.
▶️ Subscribe to My YouTube Channel (172K+ subscribers): Java Guides on YouTube
Ownership: Java EE was initially developed by Sun Microsystems and later overseen by Oracle.
Components: Java EE included technologies like Servlets, EJB (Enterprise JavaBeans), JPA (Java Persistence API), JMS (Java Message Service), JSF, and more.
Versions: The last version under the Java EE name was Java EE 8.
Jakarta EE
Ownership: Jakarta EE is managed by the Eclipse Foundation, with the support and collaboration of various industry partners.
Components: Jakarta EE maintains compatibility with Java EE but allows for more open development and potential future changes to the specifications.
Licensing and Branding: The transition to Jakarta EE required changes in licensing and naming due to legal restrictions on the Java name, which remains a trademark of Oracle.
Versions: Jakarta EE 8 was the first official release under the new stewardship, maintaining compatibility with Java EE 8.
Here's a table summarizing the key differences:
Feature | Java EE | Jakarta EE |
---|---|---|
Definition | Enterprise extensions to Java SE | Continuation of Java EE under the Eclipse Foundation |
Ownership | Initially Sun, later Oracle | Eclipse Foundation |
Components | Servlets, EJB, JPA, JMS, etc. | Continues Java EE specs, with potential future changes |
Licensing & Branding | Trademark of Oracle | New licensing and naming under Eclipse |
Versions | Ended with Java EE 8 | Started with Jakarta EE 8, maintaining compatibility |
Comments
Post a Comment
Leave Comment