I went through the Xalan-J SAX examples and I was looking for a
ContentManager or XMLFilter example which might show this, but I didn't
come across anything. Do you know of a 'SAX "tee" fitting'
implementation/example we could leverage?
Joseph Kesselman wrote:
Xalan should be noticably more efficient when processing from a SAX or
stream source (ie, when you let it build a DTM) than when processing from a
DOM.
Similarly, Xalan's native output is SAX. If you want to both serialize and
further process, you might want to consider a SAX "tee" fitting -- a SAX
stage which routes its input both to a serializer and to additional
processing -- rather than building a DOM tree.
None the less, your performance should be better than what you're
reporting, unless you're in a situation where you're swapping yourself to
death...
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Edward L. Knoll Phone (FedEx) : (719)484-2717
e-mail (FedEx) : [EMAIL PROTECTED]
e-mail (personal) : [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
