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] http://xerces.apache.org/xerces2-j/xni.html [2] http://xerces.apache.org/xerces2-j/faq-xni.html#faq-3 Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org "Dominik Rauch" <e0825...@student.tuwien.ac.at> wrote on 27/09/2012 04:25:09 PM: > 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 not fit into memory. > > There are some ideas and/or commercial products (like xDB), however, > no open-source solution yet. > > 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 positive 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. > Technical University of Vienna
