RE: [xsl] What is the fastest XSLT parser

Subject: RE: [xsl] What is the fastest XSLT parser
From: "bryan" <bry@xxxxxxxxxx>
Date: Fri, 18 Oct 2002 13:45:00 +0200
If something is taking 30 hrs on msxml then I think you've probably got
a code problem, there's likelihood of stack overflow with msxml if
recursion is improperly used.

As a general rule msxml is pretty fast. By which I mean it tends to be
the fastest in most use cases I see. Notice the 'I see' delimiter on
that statement. Speed ain't everything though.

 Your node functions I'm betting are node-set() functions which is an
extension function, i.e msxml:node-set($mynode)/*

Works if msxml is a prefix associated with the namespace
"urn:schemas-microsoft-com:xslt" in msxml, however this does not mean
you can just switch your namespace declaration to xalan as xalan does
not name it's node-set function node-set() but rather nodeset(); thus if
you want your xslt to run on both processors you should use xsl:fallback
and function-exists() etc. to provide a fallback mechanism for the cases
when using a processor that does not support mynamespace:node-set()

Xalan currently supports exslt

therefore it should be possible to switch your namespace to the exslt
namespace and in that way escape from the problem of having a node-set
function named nodeset and not node-set()

-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Thomas V.
Sent: Friday, October 18, 2002 1:23 PM
To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
Subject: [xsl] What is the fastest XSLT parser

What is the fastest XSLT parser on a Windows 32-bit platform.

So far I have tried Microsoft's Command-line utility, which invokes what
ever version of MSXML there is installed.
But a job on this one, that took 30 hours took only 5 minutes in
Xalan/Xerces testXSLT command-line utility.

However, I still have to figure out, that when I use these parsers as
command-line, some of my XLST Node Functions doesn't work properly, but
I use XMLSpy that again uses MSXML, the result is okay.

That's a bit annoying not to be able to rely on the result 100%


 XSL-List info and archive:

 XSL-List info and archive:

Current Thread