Hi, On Wed, 05 Mar 2003 18:00:23 +0100 J.gen Sieben <[EMAIL PROTECTED]> wrote: > Sounds mean, but no comes the astonishing part: It works... At least with > the XMLSpy built-in processor. What makes this example mean, is that it > doesn't work in other processors. > > Xalan-J produces an error that says that variable <var> has to reference a > nodeset. So I feel that my problem is to 'cast' my <var>-string to an > element. > Am I right with that? And how can I achieve that? This is XSLT1.0 distinction. To avoid this problem, for example, EXSLT common function 'node-set()'. http://exslt.org/exsl/index.html EXSLT is a community initiative to provide extensions to XSLT supported by Xalan, Saxon, 4suite, and so on. (but ... XmlSpy built-in processor cannot use this extention) p.s. XMLSpy Ver.5 release.3 built-in processor can handle result tree fragment like XSLT2.0's temporary node set. --------- Sougo Tsuboi [EMAIL PROTECTED] Knowledge Media Laboratory, TOSHIBA R&D Center.
