Subject: [xsl] shouldn't work but it does? From: bry@xxxxxxxxxx Date: Thu, 5 Feb 2004 21:49:36 CET |
using msxml 4, the following extension function works on msxsl.exe command line tool: function returnNSET(){ var testnsset; testnsset= "<tag>blah</tag>"; var xmlDoc = new ActiveXObject ("Msxml2.DOMDocument.4.0"); xmlDoc.async = false; xmlDoc.loadXML(testnsset); return xmlDoc; } so I can do <xsl:copy-of select="n:returnNSET ()"/> I don't know if I would consider it exactly wrong that it does this, although it is not exactly following Microsoft's documentation. Of course using the stylesheet via a processing instruction returns the error 'parameter incorrect' This is in no way improved by changing it to the correct return xmlDoc.xml; however if I do that and then change my copy-of to the the following: <xsl:apply-templates select="msxsl:node-set (n:returnNSET())"/> then I get what I would expect from the documentation - an escaped string. now I don't necessarily need the stylesheet to run anywhere but the commandline, but it might be nice to have that possibility. by the way, anyone have any example msxml extensions using ActivePerl? I am really in great need of them for this test. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] msxml and perlscript, Conor Ryan | Thread | [xsl] Pattern Matching a sting valu, scott gabelhart |
Re: [xsl] Conditional processing of, Markus Vaterlaus | Date | RE: [xsl] dynamic sorting, Peter Billen |
Month |