On 13/12/03 11:01 AM, "David Carlisle" <davidc(_at_)nag(_dot_)co(_dot_)uk>
wrote:
thanks David this works but my problem still exists
you still have lots of examples of the problem I mentioned before.
<xsl:for-each select="$rootnode//component">
That line can only work if $rootnode variable holds a node set but you
define it like
<xsl:with-param name="rootnode">
<xsl:value-of select="/DATA/component"/>
</xsl:with-param>
so its not a node set (you have to use the select attribute of
with-param)
its a result tree fragment consisting of a root note, and a text node
with the string value of whatever is in your component element.
Is there somewhere I can find an example of the difference between a node
set and a result tree fragment?
Is a node set just a "path", or set of nodes with only one "destination"
node vs. a result tree that gives multiple node sets?
/johnny :)
--
Pay no attention to that man behind the curtain.
-- The Wizard of Oz
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list