On 25 May 2005, at 08:33, Michael Kay wrote:

The processing instruction is defined as part of the JAXP specification. If you define the Result of a JAXP transformation as a ContentHandler, the transformation engine is supposed to tell the ContentHandler about disable-output-escaping using these processing instructions, and the ContentHandler is supposed to recognize them. This is because the ContentHandler is acting as your serializer, so disable-output-escaping will have no effect unless the ContentHandler knows about it.
 
I'm afraid I've no idea why upgrading JBoss should have caused this change, since I know nothing about how the transformation is being invoked. You seem to have switched from a ContentHandler that understands and implements disable-output-escaping to one that doesn't.
 
Michael Kay

Michael,
in regards to the problem I mentioned in my earlier post, the problem has been documented elsewhere with a solution as well:

http://blog.reverycodes.com/archives/000034.html

You may want to look into this ;-)

regards