[jdom-interest] JDOM and XSL/ problem with xalan 2 DO5

[Marco.Mistroni at nokia.com]

hi,
	yeah.... now i am little confused

according to an article appeared on JavaWorld,  
' JDOM takes the best concepts from DOM and SAX.[...] it does not require
the entire document to be in memory... '

so...are you saying that in pmnace evaluation, JDOM is still behind other
parsers????
can i have more clarification on that???

thanx in advance and regards
	marco


> -----Original Message-----
> From: ext Shaun Smith [mailto:shauns at pixology.com]
> Sent: 25. January 2001 13:32
> To: 'Marco.Mistroni at nokia.com'; Shaun Smith
> Cc: xalan-dev at xml.apache.org; Scott.Boag at lotus.com
> Subject: RE: [jdom-interest] JDOM and XSL/ problem with xalan 2 DO5
> 
> 
> Sorry, I think I must be misunderstanding - I am sure that
> I'll be corrected tho'!
> 
> --> Create a SAXBuilder ( SAXBuilder in memory )
> SAXBuilder builder = new SAXBuilder();
> 
> --> Create an org.jdom.Document from the builder - this is an 
> in memory
> representation
> --> similar to the DOM tree
> Document doc = builder.build(new File(args[0]));
> 
> --> Create a DOMOutputter and create an w3c.dom.Document - we 
> now have two
> representations
> --> of the tree in memory ( the JDOM document and the W3C document )
> DOMOutputter out = new DOMOutputter();
> org.w3c.dom.Document doc2 = out.output(doc);
> 
> To avoid having the w3c.dom.Document tree in memory during 
> the transform,
> you can use the Xalan SAXSource.
> 
> JDOM always constructs a tree in memory; see a few posts below
> about parsing 16mb files.
> 
> Shaun.
> 
> <SNIP>
>