Hi,
If you were to use XNI (or SAX for that matter) you're not really writing
a parser. Your DOM builder would be an event handler which responds to
callbacks to build the DOM.
The Xerces DOM builder isn't lazy. It reads the whole XML document into
memory before returning control to the user.
Hi Michael!
XNI sounds neat, but do you really think we need to write our own parser as
well? We want to parse XML just as everybody else does, we just want it to
do that lazily - like the lazy Xerces parser. It would just be importatn to
be able to reload some parts later on in case we've dismis
j-users@xerces.apache.org; Dominik Rauch
Subject: Re: Lazy DOM with regards to memory usage
Would it be sufficient to specify your DOM's Document implementation class
to the JAXP DocumentBuilderFactory using the factory's setAttribute method?
See the first example here:
http://xerces.ap
Would it be sufficient to specify your DOM's Document implementation
class to the JAXP DocumentBuilderFactory using the factory's
setAttribute method? See the first example here:
http://xerces.apache.org/xerces2-j/properties.html
On 9/27/2012 1:25 PM, Dominik Rauch wrote:
> Hello Xerces-List!
Hi,
Have you had a read through the XNI manual [1]? This is the framework on
which all parsers in Xerces are built-on.
You should be able to reuse much of that infrastructure, in particular the
existing XMLParserConfigurations [2] which are the real guts of a parser
in Xerces.
Thanks.
[1] ht
