Quelle: https://blogs.eclipse.org/post/wayne-beaton/renaming-java-ee-specifications-jakarta-ee

• Replace “Java” with “Jakarta” (e.g. “Java Message Service” becomes “Jakarta Message Service”);
• Add a space in cases where names are mashed together (e.g. “JavaMail” becomes “Jakarta Mail”);
• Add “Jakarta” when it is missing (e.g. “Expression Language” becomes “Jakarta Expression Language”); and
• Rework names to consistently start with “Jakarta” (“Enterprise JavaBeans” becomes “Jakarta Enterprise Beans”).

Das heißt:

• Jakarta APIs for XML Messaging
• Jakarta Architecture for XML Binding
• Jakarta API for XML-based Web Services
• Jakarta Common Annotations
• Jakarta Enterprise Beans
• Jakarta Persistence API
• Jakarta Contexts and Dependency Injection
• Jakarta EE Platform
• Jakarta API for JSON Binding
• Jakarta Servlet
• Jakarta API for RESTful Web Services
• Jakarta Server Faces
• Jakarta API for JSON Processing
• Jakarta EE Security API
• Jakarta Bean Validation
• Jakarta Mail
• Jakarta Beans Activation Framework
• Jakarta Debugging Support for Other Languages
• Jakarta Server Pages Standard Tag Library
• Jakarta EE Platform Management
• Jakarta EE Platform Application Deployment
• Jakarta API for XML Registries
• Jakarta API for XML-based RPC
• Jakarta Enterprise Web Services
• Jakarta Authorization Contract for Containers
• Jakarta Web Services Metadata
• Jakarta Authentication Service Provider Interface for Containers
• Jakarta Concurrency Utlities
• Jakarta Server Pages
• Jakarta Connector Architecture
• Jakarta Dependency Injection
• Jakarta Expression Language
• Jakarta Message Service
• Jakarta Batch
• Jakarta API for WebSocket
• Jakarta Transaction API

Ähnliche Beiträge

• Überblick: Aktuelle Versionen der Java EE 7 Technologien
• GlassFish v3 und Java EE 6 freigegeben
• CDI geht von Red Hat zur Eclipse-Foundation
• Java EE 6 — das Spiel geht weiter
• JSRs für Java 7 und Java 8 wurden dem JCP übergeben