Ah, no. The DOM passed to Xalan (via a Document) does not contain the xml declaration. The declaration does appear in the output stream (within attribute values) return from the transformer.
The desired output is method=html. However, there is always the creation of a text output properties object within TransformerImpl, no matter your output method -- I gather this is for the purposes of serializing both method=text as well as attribute nodes.
The [intermittent] classloader failure is what I suspect causes these attribute values to be serialized incorrectly.
Alex
Joseph Kesselman wrote:
Thanks for tracking that down.
So if I understand your description correctly, the problem is apparently *not* that the XML declaration is appearing inside an attribute -- the attribute is being constructed by the JSP or whatever that called us -- but that the XML declaration is appearing when you thought you had selected text output, and is doing so because a classloader failure caused us to default into XML mode. Right?
Hmmm....
______________________________________ Joe Kesselman / IBM Research
