https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/ Recent content in Specification Guides on Jakarta® EE: The New Home of Cloud Native Java Hugo -- gohugo.io en webdev@eclipse-foundation.org (Eclipse Foundation) webdev@eclipse-foundation.org (Eclipse Foundation) Tue, 29 Apr 2025 00:00:00 +0000 https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/nosql-and-persistence-explained/ Tue, 29 Apr 2025 00:00:00 +0000 webdev@eclipse-foundation.org (Eclipse Foundation) https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/nosql-and-persistence-explained/ <h2 id="abstract">Abstract</h2> <p>The Jakarta EE ecosystem offers specifications for building database backend<br> applications using relational and/or NoSQL databases. The Jakarta Persistence<br> specification, with a rich history dating back almost 20 years, has been a<br> staple in the Java community for writing relational database applications. The<br> Jakarta NoSQL specification, with a short history dating back to 2020, provides<br> comprehensive support for all four types of NoSQL databases.</p> <h2 id="introduction">Introduction</h2> <p>The Jakarta EE ecosystem offers specifications for building database backend<br> applications using relational and/or NoSQL databases. The <a href="https://redesign-2025--jakartaee.netlify.app/specifications/persistence/">Jakarta Persistence</a><br> specification, with a rich history dating back almost 20 years, has been a<br> staple in the Java community for writing relational database applications. The<br> <a href="https://redesign-2025--jakartaee.netlify.app/specifications/nosql/">Jakarta NoSQL</a> specification, with a short history<br> dating back to 2020, provides comprehensive support for all four types of NoSQL<br> databases.</p> https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/concurrency-explained/ Tue, 12 Mar 2024 00:00:00 +0000 webdev@eclipse-foundation.org (Eclipse Foundation) https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/concurrency-explained/ <p>Application performance can make or break a user’s experience.<br> Applications that provide a consistent experience and perform well are<br> more likely to benefit user productivity. The Jakarta Concurrency<br> specification targets application performance and usability by providing<br> a standard API for developing concurrent application processes without<br> compromising container integrity. It is not recommended to utilize<br> traditional Java SE threads or timers within a Jakarta EE container<br> because use of threads or timers may cause reliability issues and<br> unexpected results. Jakarta Concurrency provides an API that does not<br> intrude on container integrity, but rather, uses services that are<br> managed by the container and matches the functionality provided by the<br> Java SE Concurrency Utilities.</p> https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/contexts-dependency-injection-explained/ Tue, 12 Mar 2024 00:00:00 +0000 webdev@eclipse-foundation.org (Eclipse Foundation) https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/contexts-dependency-injection-explained/ <p>Jakarta Dependency Injection provides the ability to make<br> use of contextual objects in an application with maximum<br> reusability, testability, and maintainability. This<br> specification provides a means for developers to easily<br> obtain objects throughout classes within an application<br> without the requirement to use constructors, factories, or<br> service locators.</p> <p>Jakarta Contexts and Dependency Injection, Jakarta CDI for<br> short, is one of the paramount specifications of the<br> Jakarta EE Platform, as it contains a number of powerful<br> complimentary services that are utilized across a majority<br> of Jakarta EE applications. Jakarta CDI has been known as<br> the &ldquo;glue&rdquo; for the Jakarta EE Platform because one of the<br> most significant features is the enablement of contextual<br> objects to be made available for use throughout other<br> classes and views within an application. The specification<br> makes use of the Jakarta Dependency Injection specification<br> to provide this capability, but Jakarta CDI also provides a<br> number of other features beyond dependency injection<br> including scope assignment, generation of preconfigured<br> objects, qualification, initiating code when events occur,<br> to mention a few.</p> https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/jakarta-ee-platform/ Tue, 12 Mar 2024 00:00:00 +0000 webdev@eclipse-foundation.org (Eclipse Foundation) https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/jakarta-ee-platform/ <p><strong>The Jakarta EE Platform enables developers to produce<br> lightweight, cloud native applications while providing<br> maximum developer productivity</strong>. Now featuring multiple<br> profiles geared towards producing microservices or full<br> stack applications, the Platform provides flexibility for<br> developing applications of all sizes. <strong>The Platform is<br> composed of a number of specifications, each targeting<br> specific areas in application architecture</strong>. This modular<br> approach allows the specifications to evolve under<br> different expert groups and timelines, while the platform<br> enables each to work together in harmony.</p> https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/persistence-explained/ Tue, 12 Mar 2024 00:00:00 +0000 webdev@eclipse-foundation.org (Eclipse Foundation) https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/persistence-explained/ <p>Enterprise applications typically require persistence for data storage. The<br> specification is foundational for many technologies since relational databases<br> are widely used within the industry. The Jakarta Persistence specification,<br> also known as Jakarta Persistence API (JPA), encompasses a number of APIs that<br> facilitate the creation, reading, updating, and deletion of data within data<br> stores. The specification provides an Entity Manager API which is used to<br> facilitate the lifecycle of entities within an application. The <code>Query</code> and<br> <code>TypedQuery</code> APIs are used to retrieve data utilizing both static and dynamic<br> queries. The Metamodel API enables the ability to obtain metadata regarding<br> managed entities and persistence objects. Lastly, the Criteria API provides a<br> means for defining queries through the use of object based query objects to<br> perform strongly-typed queries.</p> https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/restful-web-services-explained/ Tue, 12 Mar 2024 00:00:00 +0000 webdev@eclipse-foundation.org (Eclipse Foundation) https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/restful-web-services-explained/ <p>Jakarta REST is the solution for development of building Representational State<br> Transfer web services on the Jakarta EE Platform. The specification is easy to<br> learn, and it enables one to construct powerful REST APIs and it also includes<br> APIs for working with web services as a client. As such, this specification<br> is key to the development of microservices and cloud based applications, and it<br> is part of the Jakarta EE Web Profile as well as the full platform.</p> https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/security-authorization-and-authentication-explained/ Tue, 12 Mar 2024 00:00:00 +0000 webdev@eclipse-foundation.org (Eclipse Foundation) https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/security-authorization-and-authentication-explained/ <p>Security is a major component of application development. Jakarta EE provides<br> the robust Jakarta Security specification that when paired with the Jakarta<br> Authentication and Jakarta Authorization specifications, provides APIs that<br> deliver end-to-end security. There are a large number of application processes<br> that require security measures, and these specifications provide the ability to<br> do so in a straightforward manner using annotations and minimal XML<br> configurations. Jakarta EE compliant containers and deployment environments<br> adhere to the constructs of the Authentication and Authorization policies to<br> ensure that applications can be secured in a standard way and deployed across a<br> number of different environments.</p> https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/servlet-faces-and-server-pages-explained/ Thu, 22 Feb 2024 00:00:00 +0000 webdev@eclipse-foundation.org (Eclipse Foundation) https://redesign-2025--jakartaee.netlify.app/learn/specification-guides/servlet-faces-and-server-pages-explained/ <p>The Jakarta EE Platform offers a number of APIs that can be used to create web<br> based user interfaces. The most mature and perhaps most well known is the<br> Jakarta Servlet specification. Jakarta Servlet was first released in 1996, and<br> it enables Java developers to create web pages containing dynamic web content<br> using pure Java. The specification has changed much over the years and it is<br> able to interact with modern technologies and comply with the modern era of web<br> technologies with features such as HTTP/2. Jakarta Server Pages (JSP) was<br> first released in 1999, and it enables developers to create web based user<br> interfaces using a mixture of HTML markup and special Jakarta Servlet tags.<br> JSP enables easy creation of dynamic web views, and it has also made great<br> progressions over the years to position it for standard model-view-controller<br> development. Model-View-Controller development specifies clear separation of<br> view code from business logic, and in the early years of JSP it was common to<br> see business logic intermixed with HTML code. To that end, Jakarta Faces was<br> initially released in 2004, and it provides the ability to develop web based<br> user interfaces with XML for the view and a corresponding Java class to contain<br> the business logic for the view. This specification has adapted over the years<br> to continue as a relevant web based user interface API for modern times.</p>