I'm downloading saxonb8.3 now! Thanks for the tip, Jay.
Douglas Ross
Developer, HTML UI Framework
Kronos
E-mail: dross(_at_)kronos(_dot_)com
Voice: (978) 947-4305
Fax: (978) 256-2474
www.kronos.com
Smaller, Faster, Sharper, Easier(tm)
-----Original Message-----
From: JBryant(_at_)s-s-t(_dot_)com [mailto:JBryant(_at_)s-s-t(_dot_)com]
Sent: Friday, February 25, 2005 12:26 PM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] Help using the xsl:result-document instruction
It was exactly this feature that made me go to Saxon 8. Saxon does a
great
job of implementing it (and everything else that I've needed). I have
one
stylesheet that uses xsl:result-document to write over 1300 HTML files
(one for every element in a data warehouse). I've since incorporated a
few
other XSLT 2.0 features (most recently solving a problem with
xsl:for-each-group), but xsl:result-document was the key feature for me.
FWIW (not much)
Jay Bryant
Bryant Communication Services
(presently consulting at Synergistic Solution Technologies)
"Michael Kay" <mike(_at_)saxonica(_dot_)com>
02/25/2005 11:18 AM
Please respond to
xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
To
<xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
cc
Subject
RE: [xsl] Help using the xsl:result-document instruction
xsl:result-document is an XSLT 2.0 feature, so you need an XSLT 2.0
processor to run it. Xalan is an XSLT 1.0 processor.
I don't know why Xalan hasn't given you any error messages.
Michael Kay
http://www.saxonica.com/
-----Original Message-----
From: Ross, Douglas [mailto:DRoss(_at_)Kronos(_dot_)com]
Sent: 25 February 2005 17:09
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] Help using the xsl:result-document instruction
Newbie User: I am not able to use xsl:result-document to
write output to
another file. There are no error messages. Any insight or pointers is
much appreciated.
My guess is my environment is not set up correctly. Am I missing
something on the class path or the extension dirs? The
checkEnvironmentExtension output is below.
The command line to invoke the XSLT script:
E:\test>java org.apache.xalan.xslt.Process -XSL test.xslt
The contents of test.xslt:
<?xml version="1.0"?>
<xsl:stylesheet version="2.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
<xsl:output
method="xml"
escape-uri-attributes="no"
omit-xml-declaration="no"
encoding="UTF-8"
indent="yes"
/>
<xsl:template match="/">
<before/>
<!-- write to another file -->
<xsl:result-document href="test.xml"
method="xml">
<inside/>
</xsl:result-document>
<after/>
</xsl:template>
</xsl:stylesheet>
The environment check output:
<checkEnvironmentExtension>
<EnvironmentCheck version="$Revision: 1.26 $">
<environment>
<item key="version.DOM.draftlevel">2.0fd</item>
<item
key="java.class.path">;C:\Development\xalan-j_2_6_0\bin\bsf.ja
r;C:\Devel
op
ment\xalan-j_2_6_0\bin\xalan.jar;C:\Development\xalan-j_2_6_0\
bin\xerces
Impl.jar
;C:\Development\xalan-j_2_6_0\bin\xml-apis.jar;</item>
<item key="version.JAXP">1.1 or higher</item>
<item key="java.ext.dirs">C:\Program
Files\Java\jre1.5.0_01\lib\ext</item>
<item key="version.xerces2">Xerces-J 2.6.2</item>
<item key="version.xerces1">not-present</item>
<item key="version.xalan2_2">Xalan Java 2.6.0</item>
<item key="version.xalan1">not-present</item>
<item key="version.ant">not-present</item>
<item key="java.version">1.5.0_01</item>
<item key="version.DOM">2.0</item>
<item key="version.crimson">not-present</item>
<item key="sun.boot.class.path">C:\Program
Files\Java\jre1.5.0_01\lib\rt.jar;C:\
Program Files\Java\jre1.5.0_01\lib\i18n.jar;C:\Program
Files\Java\jre1.5.0_01\li
b\sunrsasign.jar;C:\Program
Files\Java\jre1.5.0_01\lib\jsse.jar;C:\Program Files
\Java\jre1.5.0_01\lib\jce.jar;C:\Program
Files\Java\jre1.5.0_01\lib\charsets.jar
;C:\Program Files\Java\jre1.5.0_01\classes</item>
<foundJar desc="path"
name="xalan.jar">C:\Development\xalan-j_2_6_0\bin\xalan.ja
r</foundJar>
<foundJar desc="apparent.version" name="xercesImpl.jar">xercesImpl.jar
from Xerc
es-J-bin.2.6.2</foundJar>
<foundJar desc="path"
name="xercesImpl.jar">C:\Development\xalan-j_2_6_0\bin\xer
cesImpl.jar</foundJar>
<foundJar desc="apis.jar-apparent.version"
name="xml">xml-apis.jar from
tck-jaxp
-1_2_0 branch of xml-commons, tag:
xml-commons-external_1_2_01</foundJar>
<foundJar desc="apis.jar-path"
name="xml">C:\Development\xalan-j_2_6_0\bin\xml-a
pis.jar</foundJar>
<item key="version.SAX">2.0</item>
<item key="version.xalan2x">Xalan Java 2.6.0</item>
</environment>
<status result="OK"/>
</EnvironmentCheck>
</checkEnvironmentExtension>
Sorry for the simple question but I was not able to find much through
google and there were only 7 posts in the xsl-list archives
which didn't
help me. The only mention of result-document in the
distributed docs is
the history.html file which shows the commit entry.
Any help is greatly appreciated.
Douglas Ross
Developer, HTML UI Framework
Kronos
E-mail: dross(_at_)kronos(_dot_)com
www.kronos.com
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--