DOM Level 3 Load and Save

Chris Burdess <[email protected]>
Newsgroups gmane.comp.java.classpath.extensions.xml
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There is most of a DOM Level 3 Load and Save implementation for GNU DOM 
(the LSSerializer implementation should be generic enough for any DOM 
implementation, including libxmlj) now in CVS.

This implementation supports serializer filters, and will shortly 
support parser filters.

The LSParser implementation is not based on gnu.xml.pipeline, due to 
the slightly different requirements of  the LS interface. It also has 
the potential for slightly better performance than gnu.xml.pipeline, 
since it deals exclusively with GNU DOM trees.

This therefore begs the question: should we use the LS interface for 
the JAXP DocumentBuilder implementation for GNU DOM? Are there people 
using the pipeline classes who can see some advantage in staying with 
them instead?
- -- 
Chris Burdess
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFBmQFd6dl1DEqHgrgRAvvWAJ9avGLkbdxulSIsoeqwI2GP/qxlBACcC2Fo
668IaskRO7kcJTZcJ4rlc/U=
=aQB5
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.