This is the mail archive of the xsl-list@mulberrytech.com mailing list .

Index Nav: [Date Index] [Subject x] [Author Index] [Thread Index] /tr>
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread&nbext] 
Hi Mike,

Mike said:
No, it was just an example. I didn't want to provide examples of every
possible use of the dont() function, so I picked the one that in my
opinion was the most useful. If you are going to be referring to a document
mule times, it makes more sense to only call document() once and bind
the node-set it returns to a variable, then refer to thariable.

Like any other function, it returns an object of one of the types: node-set,
number, boolean, string, result tree fent. You know that it returns a
node-set, so you can use it anywhere where you expect to see a node-set. So
it could be the t location step in an XPath expression. I am not aware
of any XSL processors (aside from IE) that would have any trouble witat.

Didier replies:
What I wanted to know is if constructs like:
 <....
select="document('http://remoteserver/file.xml')/path/to/some/nodes"/>
and
 <....
select="document(./any/xpath/node/@andAttrib)/path/to/some/nodes"/>

are working well in XSLT engines and if yes in which (after some testing, so
that we know for suhat it is well supported)

I can say that in MSXML2 it is not (not yet supported)
I can say that in XT both constructs are srted
I do not know about Saxon?
I do not know about Xalan?


Cheers
Didier PH Martin
------------------------------------------
Email: martind@netfolder.com
Conferences: Web New York (http://www.mfweb.com)
Book: Pro published by Wrox Press
Products: http://www.netfolder.com


 XSL-List info and ive:  http://www.mulberrytech.com/xsl/xsl-list
Index Nav:
[Date Index] [Subject Index] [Author Index] [Threbsp;Index]
Message Nav: [Date Pre>] [Date Next] [Thread Prev] [Thread Next]
-X-User-Footer-End-->