Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Re: Mega XSLT Batch job - best approach?

by stefan k (Curate)
on Jan 22, 2002 at 18:18 UTC ( #140660=note: print w/replies, xml ) Need Help??

in reply to Mega XSLT Batch job - best approach?

Java start up on Saxon makes it massivly slower to run

Hmm, have you not tried to process the large nested XML file? I found the Java-Startup very slow, too, but afterwards saxon runs fine. You can always create a new outputfile from saxon by using something like

<xsl:template match="page"> <saxon:assign name="ofile"> <xsl:value-of select="@outputfile" /> </saxon:assign> <saxon:output file="{$ofile}" method="html" indent="yes" doctype-public="-//W3C//DTD HTML 4.01 Transitional//EN" doctype-system="" encoding="iso-8859-1"> <!-- ... process contents here --> </xsl:template>
and so on. This assumes you defined a saxon variable. And you should have a look at the correct syntax when you're using newer Saxon versions. This syntax is a snippet I use with Saxon 5.5.1 which is from a time when the official W3C XSLT did not support multiple outputfiles.

I build my whole site from one large XML (about 200k) file and it processes in some 10 seconds on a Athlon 1.4 512MB linux box - including the java startup.

Yes I know that this is not a perlish solution. Maybe you should look at

Regards... Stefan
you begin bashing the string with a +42 regexp of confusion

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://140660]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (3)
As of 2017-05-28 02:05 GMT
Find Nodes?
    Voting Booth?