Greetings Specification Committee.
I've listed the specifications for which I have
received approval to contribute at the bottom of
this message. As we did with the Full and Web
Profile documents, I will contribute the document to
the corresponding project team via IPZilla. The IP
Team is standing by push these contributions through
their vetting process (which should only take a few
minutes for each document).
I stand ready to start contributing these
documents when the Specification Committee gives me
the "go ahead" (recall that we need to give the
project teams some guidance regarding what we expect
them to do with these documents; i.e., what
specifically needs to be done to to "Jakartify" the
document).
With these documents in hand, I believe that
there are three possible courses of action for each
project team:
- Ignore it;
- Jakartify the document and make it available
as a service release; or
- Jakartify the document, add new content, and
make it available as a new Final Specification.
For a service release, per the process, ballot
approval from the Specification Committee is
required. With approval in place, the project team
can update their existing /specification record
with a reference to the new document (the
Specification Committee may need to provide some
guidance regarding how this manifests).
For a new Final Specification, the project team
will need to first engage in a Plan Review, and the
rest of the process, culminating in a Release Review
and the creation of a new /specification record
representing the new version.
Strictly speaking, a project team can engage in
the Jakartification of the document without
immediately engaging in any reviews (i.e., just
update the document and leave it in the repository).
In this event, it would need to be made clear that
the Jakartified document cannot be used to create an
implementation until after it is ratified as a Final
Specification.
I can expand on any of these options if
necessary.
Jakarta EE Full Profile
Jakarta EE Web Profile
Jakarta Annotations
Jakarta Enterprise Beans
Jakarta _expression_ Language
Jakarta Security
Jakarta Server Faces
Jakarta Interceptors
Jakarta Authorization
Jakarta Activation
Jakarta Managed Beans
Jakarta Deployment
Jakarta XML RPC
Jakarta Authentication
Jakarta Mail
Jakarta XML Binding
Jakarta RESTful Web Services
Jakarta Web Services Metadata
Jakarta XML Web Services
Jakarta Connectors
Jakarta Persistence
Jakarta JSON Binding
Jakarta JSON Processing
Jakarta Debugging Support for Other Languages
Jakarta Server Pages
Jakarta Transactions
Jakarta WebSocket
Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
![]()
