Custom Transformer InputSource

[Anthony Rabaa <ar...@amconresearch.net>]

Hello,

I'm looking for advice on a better solution to my problem.  In short, I 
need to keep character references unresolved.  The Xerces SAXParser 
object may have a LexicalHandler and ContentHandler attached and with 
those I can easily catch the entities and push them through.  The same 
solution is also possible for the SAXResult object, but not the 
SAXSource for understandable reasons.  My current solution requires a 
custom DOM builder using a SAX parser, ContentHandler and a 
LexicalHander object.  Using this I can supply the DOM without resolved 
character references as a DOMSource object to the Transformer and 
hopefully transform the document without a problem.

I find this solution a little bloated.  Hopefully somebody may be able 
to point me in a better direction.  Thanks in advance for your advice!
-- 
   *Anthony Rabaa*
   Software Developer & Network Administrator
    AMCon Research Inc.
    Ottawa, Ontario, Canada
    http://www.amconresearch.net

Re: Custom Transformer InputSource

[Joseph Kesselman <ke...@us.ibm.com>]

Character references and entity references are not part of the XPath data
model; Xalan is not able to directly manipulate them.

______________________________________
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