Editing Jakarta EE (section)

== Specifications ==
Jakarta EE includes several specifications that serve different purposes, like generating web pages, reading and writing from a database in a transactional way, managing distributed queues.

The Jakarta EE APIs include several technologies that extend the functionality of the base [[Java Platform, Standard Edition|Java SE]] [[Application programming interface|API]]s, such as [[Jakarta Enterprise Beans]], [[Jakarta Connectors|connectors]], [[Jakarta Servlet|servlet]]s, [[Jakarta Server Pages]] and several [[web service]] technologies.

=== Web specifications ===
* [[Jakarta Servlet]]: defines how to manage HTTP requests, in a synchronous or asynchronous way. It is low level and other Jakarta EE specifications rely on it;
* Jakarta WebSocket: API specification that defines a set of APIs to service [[WebSocket]] connections;
* [[Jakarta Faces]]: a technology for constructing user interfaces out of components;
* [[Jakarta Expression Language]] (''EL'') is a simple language originally designed to satisfy the specific needs of web application developers. It is used specifically in Jakarta Faces to bind components to (backing) beans and in Contexts and Dependency Injection to named beans, but can be used throughout the entire platform.

=== Web service specifications ===
* [[Jakarta RESTful Web Services]] provides support in creating web services according to the [[Representational State Transfer]] (REST) architectural pattern;
* Jakarta JSON Processing is a set of specifications to manage information encoded in JSON format;
* Jakarta JSON Binding provides specifications to convert JSON information into or from Java classes;
* [[Jakarta XML Binding]] allows mapping XML into Java objects;
* [[Jakarta XML Web Services]] can be used to create SOAP web services.

=== Enterprise specifications ===
* Jakarta Activation (''JAF'') specifies an architecture to extend component Beans by providing data typing and bindings of such types.
* Jakarta Contexts and Dependency Injection (''CDI'') is a specification to provide a [[dependency injection]] container;
* [[Jakarta Enterprise Beans]] (''EJB'') specification defines a set of lightweight APIs that an object container (the EJB container) will support in order to provide [[Transaction processing|transactions]] (using [[Jakarta Transactions|JTA]]), [[remote procedure call]]s (using [[Java remote method invocation|RMI]] or [[RMI-IIOP]]), [[concurrency control]], [[dependency injection]] and [[access control]] for business objects. This package contains the Jakarta Enterprise Beans classes and interfaces that define the contracts between the enterprise bean and its clients and between the enterprise bean and the ejb container.
* [[Jakarta Persistence]] (''JPA'') are specifications about object-relational mapping between relation database tables and Java classes.
* [[Jakarta Transactions]] (''JTA'') contains the interfaces and annotations to interact with the transaction support offered by Jakarta EE. Even though this API abstracts from the really low-level details, the interfaces are also considered somewhat low-level and the average application developer in Jakarta EE is either assumed to be relying on transparent handling of transactions by the higher level EJB abstractions, or using the annotations provided by this API in combination with CDI managed beans.
* [[Jakarta Messaging]] (''JMS'') provides a common way for Java programs to create, send, receive and read an enterprise messaging system's messages.

=== Other specifications ===
* Jakarta Validation: This package contains the annotations and interfaces for the declarative validation support offered by the [[Jakarta Validation]] API. Jakarta Validation provides a unified way to provide constraints on beans (e.g. Jakarta Persistence model classes) that can be enforced cross-layer. In Jakarta EE, Jakarta Persistence honors bean validation constraints in the persistence layer, while [[JavaServer Faces|JSF]] does so in the view layer.
* Jakarta Batch provides the means for [[batch processing]] in applications to run long running background tasks that possibly involve a large volume of data and which may need to be periodically executed.
* [[Jakarta Connectors]] is a Java-based tool for connecting application servers and enterprise information systems (''EIS'') as part of enterprise application integration (''EAI''). This is a low-level API aimed at vendors that the average application developer typically does not come in contact with.