Altova Mailing List Archives

Re: [xsl] copy-of too powerful or wrong

From: David Carlisle <davidc@--------->
Date: 8/9/2004 9:26:00 PM
copy-of is just wrong here, if you use copy-of rather than
apply-templates then the nodes (including all there descendents) are
copied and no templates are applied so your other templates will have no
effect. Templates are only applied if you use xsl:apply-templates.


<xsl:template match="/">
<xsl:copy-of select="@*|node()"/>

the root node / doesn't have any attributes so this is the same as

<xsl:template match="/">
<xsl:copy-of select="node()"/>

and since a root node is made implictly to hold the root you may as well
copy the one from the source and do

<xsl:template match="/">
<xsl:copy-of select="."/>

which just copies the whole document essentially unchanged.

replace this template by an identity template from teh XSLT spec or the
faq for this list, then your basic idea will work fine.


This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.