Just guessing: Xalan's internal data model is not really a DOM, though we provide a DOM-subset access layer on top of it for the convenience of extensions. You might have better results calling a SAXSerializer instead, since generating SAX output is a more natural action for the Xalan code.
One question: What are you trying to accomplish that's forcing you toward this unnatural action? If you're really trying to generate XML syntax into the string content or comments of an XML document, that's an *extremely* bad design and you should seriously consider simply inserting the nodeset as ordinary document structure, using namespaces if necessary to distinguish it from the containing document. ______________________________________ "... Three things see no end: A loop with exit code done wrong, A semaphore untested, And the change that comes along. ..." -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html)
