Editing Jakarta EE (section)

=== 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.