[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
jeb501@xxxxxxxxxxxxxxx wrote:
Hi Eugene,
This seems like a Saxon-specific inquiry to me, which is best asked on the saxon user list. The two methods are a little different, but the speed you gain by specifying the start class is negligible compared to the time required to compile your stylesheet. The difference between redirecting stdout and letting Saxon write to stdout for you is, imho, zero.
If you want to gain speed when running multiple transformations, your best bet is to use the Saxon Java API. You can reuse your compiled stylesheet which will save a significant amount of time for each transformation.
Re: [xsl] Saxon Transformation
Subject: Re: [xsl] Saxon Transformation From: Abel Braaksma <abel.online@xxxxxxxxx> Date: Mon, 05 Mar 2007 09:22:31 +0100 |
jeb501@xxxxxxxxxxxxxxx wrote:
Which of the below method is best to use, Comparing its speed of processing, effectiveness etc.,
java net.sf.saxon.Transform -o MyFile.html MyFile.xml MyFile.xsl
java -jar saxon.jar MyFile.xml MyFile.xsl > MyFile.htm
regardsEugene
Hi Eugene,
This seems like a Saxon-specific inquiry to me, which is best asked on the saxon user list. The two methods are a little different, but the speed you gain by specifying the start class is negligible compared to the time required to compile your stylesheet. The difference between redirecting stdout and letting Saxon write to stdout for you is, imho, zero.
If you want to gain speed when running multiple transformations, your best bet is to use the Saxon Java API. You can reuse your compiled stylesheet which will save a significant amount of time for each transformation.
Cheers, -- Abel
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Saxon Transformation, jeb501 | Thread | [xsl] Xsl:copy-of writes xmlns:xsi , binu.idicula |
[xsl] Saxon Transformation, jeb501 | Date | [xsl] Xsl:copy-of writes xmlns:xsi , binu.idicula |
Month |