Altova Mailing List Archives


RE: [xsl] Applying stylesheets externally

From: "Stuart Celarier" <stuart@----------->
To:
Date: 5/14/2002 5:37:00 AM
>The best way to ensure that the client will be able to run your XSLT
>IMHO is to simply autoinstall the MSXML3 parser (or above).

Actually, installing a version of MSXML above 3.0 (that would be limited
to MSXML 4.0 at present) will _not_ ensure the client will be able to
run an XSLT processor. Objects in MSXML 4.0 can only be created using
version-dependent class names (e.g., Msxml2.DOMDocument.4.0).

If you code against a specific version of MSXML (e.g., using
Mxsml2.DOMDocument.3.0) then the code will fail unless that specific
version is installed on the client machine. If you code against the
version-independent class names (e.g., Msxml2.DOMDocument), then MSXML
3.0 is the last version that supports those classes. Additionally, MSXML
3.0 is the first version supports XSLT 1.0 (as opposed to the obsolete
WD-xsl language). That kind of limits some options.

For a fuller explanation see
http://www.perfectxml.com/articles/xml/XsltInMsxml.asp. 

Cheers,
Stuart


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.