Subject:Saxon as external xslt processor gives error when source is rdbxml Author:Paul Hermans Date:23 Mar 2006 10:13 AM
a) "licobecu.rdbxml" with an SQL/XML query leading to a query result, which is serialised as file "tussen.xml"
b) xslt run with saxon as external xslt processor with "tussen.xml" as source runs fine
b) the same xslt with saxon as external xslt processor but with source "licobecu.rdbxml" throws following error:
Error on line 2 column 1 of file:/C:/DOCUME~1/PAUL~1.HER/LOCALS~1/Temp/IDE92.xml:
SXXP0003: Error reported by XML parser: Content is not allowed in prolog. Transformation failed: Run-time errors were reported ...done
Opening the file "IDE.xml" in Stylus doesn't raise well-formdness errors.
Subject:Saxon as external xslt processor gives error when source is rdbxml Author:Minollo I. Date:23 Mar 2006 10:30 AM
When you say "external XSLT processor", do you mean Saxon configured manually in the XSLT scenario information, specifying its command line?
.rdbxml only work if the Stylus Studio URI resolver is used; and we configure Saxon to use that by default when you choose the bundled Saxon processor; but we can't do that when a processor is configured as an external engine.
If you generated Java code for an XSLT configured to use the bundled Saxon processor, Stylus Studio will generate all the needed code to make things work, and you can reuse in your own application (XSLT > Generate Java code).
BTW, if you are dealing with large relational datasets, you may want to investigate XQuery (and DataDirect XQuery, that you can use from inside Stylus Studio - http://www.datadirect.com/xquery).