>Archive Index
>xsl-list Archive Home
>Recent entries

>Thread Prev - [xsl] Saxon Transformation
>Thread Next - [xsl] Xsl:copy-of writes xmlns:xsi always - Any way to avoid this?

Re: [xsl] Saxon Transformation

From: Abel Braaksma <abel.online@--------->
To:
Date: 3/5/2007 8:25:00 AM

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

>Thread Prev - [xsl] Saxon Transformation
>Thread Next - [xsl] Xsl:copy-of writes xmlns:xsi always - Any way to avoid this?

>Archive Index
>xsl-list Archive Home
>Recent entries

Altova Mailing List Archives

Re: [xsl] Saxon Transformation