Hi All.
I am writing xsl file that will catch some nodes
(according given XPath) and will output these nodes
as a string.
Here is the code snippet that outputs the
matching node:
<xsl:text><</xsl:text>
<xsl:value-of
select="concat(name(),' ')"/>
<xsl:for-each
select="@*">
<xsl:value-of select="name()"/>
<xsl:text>="</xsl:text>
<xsl:value-of select="."/>
<xsl:text>" </xsl:text>
</xsl:for-each>
<xsl:text>></xsl:text>
So, if, for example, the node <img
src="" alt=""/> is caught, then it will be output as is.
When I was running this xsl using batch file,
everything was OK.
Now I am running it using Cocoon, and although I
get correct nodes caught, for each node all attributes are output in the reverse
order, e.g. for the previous example the result in Cocoon is
<img alt="" src=""/>
This is not a disaster, but it is rather
frustrating, because I would want to copy this node and search it in the code,
but if the attributes are reversed, I wouldn't be able to do
it.
Does anybody know why Cocoon reverses attributes
order when outputting a node?
Thank you very much for help.
Anna
|
- RE: Cocoon reversing element attributes at output? Anna Afonchenko
- RE: Cocoon reversing element attributes at output? William Brogden
- Re: Cocoon reversing element attributes at output? Steven Noels