You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by John Gentilin <ge...@eyecatching.com> on 2004/08/24 09:04:12 UTC
More extension element evaluation woes
<xsl:copy>, <xsl:attribute>, and <xsl:text> all specify template body as the child
element specification, but only <xsl:copy> will allow extension elements as part of
its child elements. The others throw an error, "Element xxx not alowed in this position"
but I can wrapper the extension elements in an <xsl:copy> and it will work corectly.
i.e.
FAILS
<xsl:attribute name="href">
<myExt:getLink/>
</xsl:attribute>
FAILS
<xsl:attribute name="href">
<xsl:text>
<myExt:getLink/>
</xsl:text>
</xsl:attribute>
WORKS
<xsl:attribute name="href">
<xsl:copy>
<myExt:getLink/>
</xsl:copy>
</xsl:attribute>
Where myExt:getLink generates characters. I think this behaviour is incorrect ??
Is this true ??
Thanks
John G
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org