Note, this mailing list does not allow replies currently. There appears
to be a bug in Netadmin that won't let me enable this. I will file a
service desk request.
Tom
-------- Original Message --------
Subject: Minutes from April 3rd StaX discussion.
Date: Sun, 06 Apr 2003 21:00:27 -0400
From: Thomas John Kincaid <kincaid_at_east.sun.com>
Reply-To: kincaid_at_east.sun.com
Organization: Sun Microsystems
To: discuss-stax_at_sun.com
Attendees:
Tom Kincaid
Phil Goodwin
Eduardo Pelegri-Llopart
Joe Fialli
Jeff Suttor
Neeraj Bajaj
We had a brief discussion about the status of JSR 173.
Update from Expert Group: Joe Fialli
-The Expert group has not met for several weeks.
-They would like to go community draft next week.
Here are the latest specs:
Latest spec, javadoc and examples are located at:
http://jse.east/~jf39279/stax/proposedCommunityDraft_April/jsr173_04_spec.pdf
http://jse.east/~jf39279/stax/proposedCommunityDraft_April/doc
http://jse.east/~jf39279/stax/proposedCommunityDraft_April/examples
Chris Fry would like to complete the JSR by this summer. We viewed this
has highly unlikely.
Navigation and Skip ability is not in the current spec. and is a source
of contention in the Expert Group.
The RI is available along with the Javadoc. This has been an
implementation first RI.
Status of our implementation: Neeraj
Neeraj said that around the end of last year they completed around 70-80
of the reader APIs. None of the writer APIs had been completed.
The status of BEA's Open Source is unknown.
Action item: Joe Fialli get the status of BEA's open source
implementation. According to Joe it was being held up by legal issues
between BEA and Sun.
We agreed that the best case scenario would be if we were able to
implement the JSR on top of Xerces. One parser for Sun would be good.
Next meeting April 17th.
Action item: Approach Roberto regarding participating in these discussions.