Printed: Mar 29, 2024
From: http://www.jcp.org/en/jsr/detail?id=173
|
Specification Leads | |||
Christopher Fry | BEA Systems | ||
Devasena Sagar | Oracle | ||
Expert Group | |||
Apache Software Foundation : Andy Clark |
BEA Systems : Larry Cable |
BEA Systems : Thorick Chow |
|
BEA Systems : Christopher Fry |
Breeze Factor, LLC : Gregory M. Messner |
Clark, James : James Clark |
|
Developmentor : Simon Horrell |
Haustein, Stefan : Stefan Haustein |
Hewlett-Packard : David Stephenson |
|
IBM : Glenn Marcy |
Intalio, Inc. : Arnaud Blandin |
Oracle : K Karun |
|
Oracle : Devasena Sagar |
Slominski, Aleksander : Aleksander Slominski |
Strachan, James : James Strachan |
|
Sun Microsystems, Inc. : Lance Andersen |
Sun Microsystems, Inc. : Joe Fialli |
Sun Microsystems, Inc. : Rajiv Mordani |
|
Contributors | |||
This JSR has been Withdrawn
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.
This JSR produced its Final Release under JCP 2.1.
Updates to the Original JSR The following information has been updated from the original request:
2016.07.26:
Following the approval of the Maintenance Review proposing the withdrawal, the Maintenance Lead withdrew this JSR.
2015.12.16:
Oracle has replaced the Maintenance Lead.
Maintenance Lead: Joe Wang
E-Mail Address: huizhe.wang
Telephone Number: +1 425 945 8760
Fax Number: -
2013.10.30:
JSR 173 moved to JCP 2.9 as part of the Maintenance process.
* Is the schedule for the JSR publicly available, current, and updated regularly?
Answer:
The JSR is currently going through a maintenance release which will be on the same schedule as the JDK 8, which is available publicly
* Can the public read and/or write to a wiki for the JSR?
Answer:
Yes – the wiki is available on the java.net project for JSR 173 at http://java.net/projects/stax-spec
* Is there a publicly accessible discussion board for the JSR that you read and respond to regularly?
Answer:
Publicly accessible mailing lists (jsr173-experts@stax-spec.java.net, users@stax-spec.java.net ) with online browsable archives have been created for JSR-173. These can be used for discussion. These are newly created as of April 2013 and I will be monitoring and responding to them regularly.
* Have you spoken at conferences and events about the JSR recently?
Answer: No
* Are you using open-source processes for the development of the RI and/or the TCK?
Answer:
The RI is an open source project on Java.net. The TCK was developed at the time of original JSR release. It is not currently available on a public open source website but can be made available if needed.
* What are the Terms of Use required to use the collaboration tools you have prepared to use with the Expert Group, so that prospective EG members can judge whether they are compatible with the JSPA?
Answer:
For future releases including maintenance release currently underway, the mailing list given above (jsr173-experts@stax-spec.java.net) may be used.
Specification license
TCK license
http://java.net/jira/browse/STAX_SPEC
2013.01.11:
Oracle has taken the Maintenance Lead role.
Maintenance Lead: Deva Sagar
E-Mail Address: deva.sagar
Telephone Number: +1 856 359 2925
Fax Number: -
2006.09.29:
The following Maintenance Lead was added:
Maintenance Lead: Thorick Chow
E-Mail Address: thorick.chow
Telephone Number: +1 415 402 7677
Fax Number: +1 415 402 7250
2006.08.04:
Maintenance Lead: Larry Cable
E-Mail Address: larry.cable
Telephone Number: +1 415 402 7639
Fax Number: +1 415 402 7250
2005.11.09:
Specification Lead: Ron Benson
E-Mail Address: rbenson
Telephone Number: +1 415 402 7552
Fax Number:
Original Java Specification Request (JSR)
Identification
| Request | Contributions | Additional
Information
Section 1. Identification
Submitting Member: BEA Systems
Name of Contact Person: Christopher Fry
E-Mail Address: christopher.fry@bea.com
Telephone Number: 415 402 7426
Fax Number: 415 402 7250
Specification Lead: Christopher Fry
E-Mail Address: christopher.fry@bea.com
Telephone Number: 415 402 7426
Fax Number: 415 402 7250
NOTE that this information has been updated from this original request.
Initial Expert Group Membership:
Section 2: Request
Two recently proposed JSRs, JAXB and JAX-RPC, highlight the need for an XML Streaming API. Both data binding and remote procedure calling (RPC) require processing of XML as a stream of events, where the current context of the XML defines subsequent processing of the XML. A streaming API makes this type of code much more natural to write than SAX, and much more efficient than DOM.
The goal of this API is to develop APIs and conventions that support processing XML as a stream. The specification will address three main areas:
Non-goals of this specification include:
SAX
To use SAX one writes handlers (objects that implement the various SAX handler APIs) that receive callbacks during the processing of an XML document. The main benefits of this style of XML document processing are that it is efficient, flexible, and relatively low level. It is also possible to change handlers during the processing of an XML document allowing one to use different handlers for different sections of the document. One drawback to the SAX API is that the programmer must keep track of the current state of the document in the code each time one processes an XML document. This creates overhead for XML processing and may lead to convoluted document processing code.
DOM
DOM provides APIs to the programmer to manipulate the XML as a tree. At first glance this seems like a win for the application developer because it does not require writing specific parsing code. However this perceived simplicity comes at a very high cost: performance. Some implementations require the entire document to be read into memory, so for very large documents one must read the entire document into memory before taking appropriate actions based on the data.
Another drawback is the programmer must use the DOM tree as the base for handling XML in the document. For many applications the tree model may not be the most natural representation for the data.
The goal will be to attempt to develop a consensus in the expert group
over the main APIs and technologies.
Section 3: Contributions
XML Data Binding Specification
http://www.jcp.org/jsr/detail/31.jsp
XML Pull Parser 2
http://www.extreme.indiana.edu/xgws/xsoap/xpp/
XML Stream API
http://e-docs.bea.com/wls/docs70/xml/xml_stream.html
Xerces XNI Pull Parser Configuration
http://xml.apache.org/xerces2-j/xni-config.html
DOM Pull Parser for Python
http://www.prescod.net/python/pulldom.html
Microsoft's XML Reader
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemxmlxmlreaderclasstopic.asp
Section 4: Additional Information (Optional)