Reason: Since version 1.0, JSR 173 StAX API has been distributed as both a standalone technology and part of the Java SE. The API has been stable without any significant changes since then and the need to use newer releases of the StAX API with shipping releases of Java SE has mostly disappeared in recent years.
In accordance with JCP 2.10 Process Document, 3.3.1.4 Platform inclusion, we are announcing the end of JSR 173 StAX Standalone distribution. After MR5, StAX 1.4, the technology that JSR 173 defines will be delivered as a part of the Java SE solely. Future changes in the StAX API will be defined through the Platform JSR.
The subsumption of the StAX API into the Platform JSR does not change any mechanisms defined in StAX. The service provider interfaces are the same except that they will then be directly specified in the Platform JSR. Deployment of alternative implementations of the StAX APIs will continue to be supported.
Nominations
Open Nominations
Nomination Type
Full Name
Biography
Spec Lead Comments
Submission Date
Spec Lead Vote
PMO Vote
Spec Lead Vote Legend
Spec Lead Vote
Description
-
Not yet reviewed/pending - The Spec Lead has not processed this nomination.
P
Processing - The Spec Lead has seen the nomination and needs more time to arrive at a decision.
N
No - The Spec Lead has decided that this nominee should not be on the JSR.
Y
Yes - The Spec Lead wants the nominee on the JSR.
PMO Vote Legend
PMO Vote
Description
-
The PMO has not yet voted on this nomination.
P
Processing - The nominee cannot yet participate on this JSR, but the legal agreements are being processed.
I
Incomplete, Illegible, or Inaccurate nomination.
XA
Missing required agreement to participate on this JSR - Addendum (ECA) Required.
XM
Missing required agreement to participate on any JSR - Not a JCP Member.
X
Not able to be on a JSR - The PMO has determined that this person cannot be on this JSR.
Y
Yes - The PMO views this as a valid nomination with a current Membership in place.
