Anthony Green wrote:
Further to confirmation by [EMAIL PROTECTED], I have committed the XML
pull parser API.
This is great - thanks!
Sun is shipping some version of these classes in 1.5:
http://java.sun.com/webservices/docs/1.5/api/javax/xml/stream/
XMLEventReader.html
But what they're shipping is different from the jsr173 stax 1.0 API:
https://stax-utils.dev.java.net/nonav/javadoc/api/javax/xml/stream/
XMLEventReader.html
It looks like you've implemented what the JDK 1.5 ships.
I downloaded woodstox (a free StAX implementation) from here:
http://woodstox.codehaus.org/Download and tried to build it against
your API implementation. It seems to require the stax 1.0 API, which
includes methods like XMLEvenReader.close().
Can we augment your API implementation to match the stax 1.0 API? Or
should we create a fork for the jsr173 implementation?
Actually what's currently in CVS is mostly JWSDP 1.5 compliant. I have
a patch locally I can apply that should make it 100% JWSDP compliant,
that's the direction I've been going in so far.
If you want me to make everything jsr173-compliant instead I can do
that, but then aren't we going to get back into a ridiculous licensing
situation with BEA? There's no way to retrieve the jsr173 specification
without agreeing to the BEA clickthrough.
Note that I will include an implementation RSN, if that's your main
issue wrt the woodstox code.
--
Chris Burdess
_______________________________________________
Classpath-patches mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/classpath-patches
