My understanding is that the SAXInputSource you describe is used to generate a XalaSourceTree for the entire document before a transformation can take place. So a DOM of sorts is created.
I guess I mis-spoke. When I said DOM what I really meant was XalanSourceTree. The point being, the entire instance is loaded into memory not parsed and translated in a more streamlike manner. If I have ~20MB instance documents to translate (and larger) my server's is going to need a _lot_ of RAM. And there will be a practical limit to the size of the documents I can handle, no? Jim > -----Original Message----- > From: Shane Curcuru [mailto:[EMAIL PROTECTED]] > Sent: Saturday, December 08, 2001 9:44 AM > To: [EMAIL PROTECTED] > Subject: Re: Sanity Check - DOMs and XSLT > > > Nope, most XSLT processors, Xalan included, work fine with either SAX > or a DOM. Check out the JAXP specs; XSLT processors that support the > JAXP API are quite happy to accept streams, SAX events, or a DOM for > any source seamlessly. > > Transformer t = transformerFactory.newTransformer(new > SAXSource(myInputSource); > // etc. > > Xalan will tend to also perform with SAX characteristics if fed SAX > events, since that's how we primarily work internally. > > - Shane > > ===== > <eof aka="mailto:[EMAIL PROTECTED]"; > BartSays="Nobody reads these anymore."/> > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com >
