I've no idea what you mean by "with no decisive structure or pattern
matching", or why you want to constrain the solution, but the obvious way to
solve your problem is by have two template rules one with match="node" and
one with match="node[(_at_)encapsulate]".
Your template, when it processes a node with no @encapsulate attribute, is
generating an element whose name is "", which will obviously fail.
Michael Kay
http://www.saxonica.com/
-----Original Message-----
From: Joris Gillis [mailto:roac(_at_)pandora(_dot_)be]
Sent: 10 February 2005 16:43
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] aborting element creation
Hi XSL guru's and experts,
I was wondering...
Is there a way (in XSLT1.0 or 2.0) to prohibit an element to be
constructed and added to the result tree, while other XSL
instruction
inside are being processed normally?
In other words, how can I transform this XML:
<root>
<node encapsulate="container"/>
<node/>
</root>
into this:
<root>
<container>
<node encapsulate="container"/>
</container>
<node/>
</root>
without any decisive structure or pattern matching?
the following template throws an error about the Qname (XSLT1.0):
<xsl:template match="node">
<xsl:element name="{(_at_)encapsulate}">
<xsl:copy-of select="."/>
</xsl:element>
</xsl:template>
Thanks in advance
--
Joris Gillis
(http://www.ticalc.org/cgi-bin/acct-view.cgi?userid=38041)
Vincit omnia simplicitas
Keep it simple
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--