Subject: Re: [xsl] node() problem From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Fri, 04 Jul 2003 13:27:30 -0400 |
Cheers, Wendell
Hi all,
A quick question:
I am using this piece of code:
<xsl:template match="@*|node()"> <xsl:element name="_r"> <xsl:attribute name="n"> <xsl:value-of select="name(.)"/> </xsl:attribute> <ind><xsl:value-of select="."/></ind> </xsl:element> </xsl:template>
To handle all of the tags not explicitly matched.
I would expect that: <foo>goo</foo>
would be transformed to
<_r n="foo"><ind>goo</ind></_r>
However the output is: <_r n="foo"><ind>goo</ind></_r> <_r n=""><ind></ind></_r>
When run through msxml, xltproc, and through Java's xslt engine. The only engine that produces the correct output is XMLSPY's transformation engine, but it is simply too slow and not practical to run on large files.
Why is it that there appears to be an "empty" node that get's matched in the first 3 engines? Is this correct and do you know a fix for it?
___&&__&_&___&_&__&&&__&_&__&__&&____&&_&___&__&_&&_____&__&__&&_____&_&&_ "Thus I make my own use of the telegraph, without consulting the directors, like the sparrows, which I perceive use it extensively for a perch." -- Thoreau
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] node() problem, Michael Kay | Thread | [xsl] [OT] Javascript help, Wendell Piez |
RE: [xsl] Re: Re: XSLT Architecture, Wendell Piez | Date | [xsl] Re: Re: Re: XSLT Architecture, Dimitre Novatchev |
Month |