>> We want to know if it is possible to replace the Xerces DOM parser
> >> with our own lazy implementation and reuse all the XPath/etc.
> >> features from Xerces or if we need to write everything from scratch.
> >>
> >> Hopefully you can give us a p
ive answer and maybe show us the
>> main extension points where we would have to fit in our
>> implementation (e.g. classes/packages we would have to re-implement
>> / derive / etc.)
>>
>>
>> Best regards,
>> D.R.
>
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
Hello Xerces-List!
We're currently thinking about writing an advanced lazy DOM implementation
compliant with the W3C DOM specification.
We know that there is already a Xerces lazy-loading-solution, however, it is
never unloading nodes, which becomes a problem for very big DOM trees which
do no
