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