Jakarta Stable APIs provides a home for stable (legacy) Jakarta EE specifications which are no longer actively developed.
Jakarta Management defines a standard management model for exposing and accessing the management information, operations, and parameters of the Jakarta EE Platform components.
Jakarta Deployment defines standard APIs that will enable any deployment tool that uses the deployment APIs to deploy any assembled application onto a Jakarta EE compatible platform.
Jakarta XML Registries describes Java API's designed specifically for an open and interoperable set of registry services that enable sharing of information between interested parties. The shared information is maintained as objects in a compliant registry. All access to registry content is exposed via the interfaces defined for the Registry Services.
Jakarta XML-based RPC defines consistent Java APIs for using XML based RPC standards.
| Repo | Commits | Reviews | Issues |
|---|---|---|---|
| https://github.com/eclipse-ee4j/enterprise-deployment | 0 | 1 | 0 |
| https://github.com/eclipse-ee4j/jax-rpc-api | 0 | 1 | 0 |
| https://github.com/eclipse-ee4j/jaxr-api | 0 | 1 | 0 |
| https://github.com/eclipse-ee4j/management-api | 0 | 1 | 0 |
The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and recommendations on open source best practices.
See the project’s PMI page at https://projects.eclipse.org/projects/ee4j.jakartaee-stable