Paul Prescod wrote:
>
> Pierpaolo Fumagalli wrote:
> >
>
> > Since with SAX 2.0 we'll be able to fully build a DOM, what about
> > "dropping" the current DOMParser and SAXParser, keeping just one of them
> > (the SAX one) and relying on a SAX-to-DOM to get the documents?
>
> I strongly support this idea. It will be useful to be able to build DOMs
> from the results of filters and XSLT transforms. This is doable if the
> DOM Builder is just another SAX event consumer.
It's working right now in SAX1, but in SAX1 I can't deal w/ stuff like
CDATA and Comments... SAX2 adds this capability, so, as soon as Xerces
will support the new SAX2 APIs, I'll convert my classes and place
them....
WHERE??? Package? (org.apache.xerces.dom? org.apache.xml.tools?)
Pier
--
--------------------------------------------------------------------
- P I E R -
stable structure erected over water to allow the docking of seacraft
<mailto:[EMAIL PROTECTED]> <http://www.betaversion.org/~pier/>
--------------------------------------------------------------------
- ApacheCON Y2K: Come to the official Apache developers conference -
-------------------- <http://www.apachecon.com> --------------------