This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: xsl: help (urgent)
- To: <XSL-List at lists dot mulberrytech dot com>, <raghu dot krishnapillai at oracle dot com>
- Subject: Re: [xsl] xsl: help (urgent)
- From: "Steve Muench" <Steve dot Muench at oracle dot com>
- Date: Tue, 10 Apr 2001 06:14:46 -0700
- References: <007e01c0c177$9aebaf60$d1a84598@idc.oracle.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
| <xsl:output method="html" disable-output-escaping="yes"
| media-type="text/html" indent="no"/>
disable-output-escaping doesn't go here.
| <xsl:value-of disable-output-escaping="yes"
Whenever it appears that disable-output-escaping="yes" is
not working, 99% of the time it is because you are:
(1) Using your own Java program to produce the results
of the XSLT transformation, and
(2) Using the wrong API to effect the transformation.
The Oracle processor has two similar API's:
(a) DocumentFragment processXSL(xsl,xml)
(b) void processXSL(xsl,xml,PrintWriter)
If you use (a), you get an in-memory tree
of XML. If you then use the DOM's print() method
to serialize it, then that's what you get. A DOM
serialization. It's not smart to all the XSLT
output serialization options.
If you use (b), then the XSLT engine gets the
chance to perform all of the appropriate XSLT
output "magic", including disable-output-escaping.
So, make sure you're using (b).
______________________________________________________________
Steve Muench, Lead XML Evangelist & Consulting Product Manager
BC4J & XSQL Servlet Development Teams, Oracle Rep to XSL WG
Author "Building Oracle XML Applications", O'Reilly
http://www.oreilly.com/catalog/orxmlapp/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list