Node-set to XML string via Java extensions in Xalan-J: possible? 2007-02-22 - By Mike Brown
keshlam@(protected) wrote:
> 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.
Ah, I might try that. Thanks.
> 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 [...]
I'm not. I'm generating *HTML* (maybe I left xsl:output method="xml" in my
sample code by mistake) and am putting part or all of the source tree, as XML
text, into a textarea. Our QA folks run our web app through thousands of test
scenarios, each of which results in a different source XML document that
affects the HTML output, sometimes in undesirable ways. The textarea gives
them the ability to provide us developers with an extremely valuable tool for
debugging: they just copy-paste the content of the textarea into their bug
report. 90% of the time it allows us to quickly reproduce their results and/or
rule out certain parts of the app as being a problem.
Mike
|
|
