This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Problem with Oracle Parser Classes vs. Command-line
- To: <xsl-list at mulberrytech dot com>
- Subject: Re: Problem with Oracle Parser Classes vs. Command-line
- From: "Steve Muench" <smuench at us dot oracle dot com>
- Date: Thu, 21 Sep 2000 15:04:01 -0400
- References: <4.3.2.7.0.20000921201220.00b167a0@192.9.200.78>
- Reply-To: xsl-list at mulberrytech dot com
This likely occurs because you are using the ./sample/XSLSample.java
sample program to accomplish the command-line transformation
instead of the correct "oraxsl" command line tool that's
provided.
Run the command-line transformation with:
$ java oracle.xml.parser.v2.oraxsl xmldoc.xml style.xsl out.html
or use the supplied ./bin/oraxsl.bat script to run the same.
Under the covers, the explanation for this is that
the XSLSample.java program uses the processXSL() method
whose signature is:
DocumentFragment processXSL(XSLStylesheet, XMLDocument)
whereas the oraxsl utility uses the processXSL() method
whose signature is:
void processXSL(XSLStylesheet, XMLDocument, PrintWriter)
The former just returns a DocumentFragment and serialization
is done by calling the print() method on the DOM object.
This case is not aware of the <xsl:output> serialization
hints.
The latter case lets the XSLT processor serialize the
result tree, using all of the <xsl:output> hints in the process.
______________________________________________________________
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/
----- Original Message -----
From: "Paul Terray" <terray@4dconcept.fr>
To: <xsl-list@mulberrytech.com>
Sent: Thursday, September 21, 2000 3:18 PM
Subject: Problem with Oracle Parser Classes vs. Command-line
| Hello everyone,
|
| I am using for a project pretty complex XSL stylesheets. I am using Oracle
| parser, because I want the Database to do the work.However, the command
| line does not give the same output as the classes used in Java servlet on
| Oracle :
|
| - The command line does not obey AT ALL at the <xsl:output> command (it
| produce XML where I ask HTML, and does not take into account my encoding).
|
| - My other problem is it does not even take into account the
| disable-escaping-output attribute of <xsl:text>.
|
| Therefore, everything goes sploing (approximately). Does anybody have seen
| this behavior and know either :
| - how to solve the problem ?
| - use another processor with Oracle ?
|
| Thanks in advance.
| --
| Paul Terray - terray@4dconcept.fr
| tel : 01 34 58 70 76
|
|
|
| XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list