[jdom-interest] RE: Keeping an XML file in memory

[citynomad]

Thanks Michael.  Could you point me to some documentation that explains how
to build a TinyTree from a file, and how to create a Source object out of it
(and which Source implementation to use)?  I am not really familiar with
Saxon's own API, as I've always used it through JAXP interfaces.

Also, I am somewhat reluctant to indroduce a direct dependency on Saxon in
my code (although I suppose since I am using some XSLT 2.0 features, I
already have it, whether I want it or not. :)  Could you provide some more
insight as to what advantages a TinyTree provides over a simple byte array
in my situation?  Is it significantly less expensive to create a Source
object from a TinyTree than from a byte array?

Thanks again.

Eugene





Michael Kay wrote:
> 
> 
> Try the Saxon TinyTree. Unlike JDOM, this doesn't allocate a Java object
> for
> each node. The structure is optimized for XPath access, and in particular,
> for a read-only tree - JDOM and similar models have extra overhead because
> of the need to support updating.
> 
> 

-- 
View this message in context: http://www.nabble.com/Keeping-an-XML-file-in-memory-tf4196500.html#a11954045
Sent from the JDOM - General mailing list archive at Nabble.com.