That's interesting, this leads me to another question...
Is there anyway to have the Xalan source tree act as a fully functional
DOM, or is it meant only for XalanTransfomer needs?
We need a way to have both XPath and full DOM functionality working - do
you know of any possible way to do this with Xalan C++?
Thank you so much for your help. - amo
Anne Marie O'Brien
NMS Communications
(508) 271-1104
"David N
Bertoni/Cambridge To: [EMAIL PROTECTED]
/IBM" cc:
<david_n_bertoni@ Subject: Re: [xsl] Does the
XalanTransformer class always resolve the
us.ibm.com> XSLTInputSource to a DOM before
applying the transformation?
05/16/2002 02:42
PM
Please respond to
xalan-dev
Xalan builds the entire source tree before processing. It does not build a
fully-functional DOM, to save space.
That said, you can always write your own source tree implementation that
builds itself incrementally.
Dave
AnneMarie_O'Brie
[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
cc: (bcc: David N
Bertoni/Cambridge/IBM)
05/16/2002 11:37 Subject: [xsl] Does the
XalanTransformer class always resolve the
XSLTInputSource to a DOM
AM before applying the
transformation?
Please respond
to xalan-dev
Apparently my questions belongs on this list...
Anne Marie O'Brien
NMS Communications
----- Forwarded by Anne Marie O'Brien/NMS Communications on 05/16/2002
02:33 PM -----
AnneMarie_O'[EMAIL PROTECTED]
Sent by: To:
[EMAIL PROTECTED]
[EMAIL PROTECTED] cc:
rrytech.com Subject: [xsl]
Does the XalanTransformer class always resolve the XSLTInputSource
to a DOM before
applying the transformation?
05/16/2002 08:54 AM
Please respond to xsl-list
Or can the transformer work on a constant feed of input data in a SAX like
way?
Thanks in advance for any information.... amo
Anne Marie O'Brien
NMS Communications
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
