RE: combining oracle node-set with msxml node-set

The strange thing is I do have such a test (shown below). Even though
there's no way that the oracle processor should reach this line it still
throws the error. It's as if oracle does some preprocessing to check that
external functions have the correct prefix.

Is this something you've managed to do?

	<xsl:choose>
		<xsl:when test="function-available('msxsl:node-test()')">
			<xsl:apply-templates
select="msxsl:node-set($tradefo)" /> 
		</xsl:when>
		<xsl:otherwise>
			<xsl:apply-templates select="ora:node-set($tradefo)"
/>
		</xsl:otherwise>
	</xsl:choose>

-----Original Message-----
From: David Carlisle [mailto:davidc@xxxxxxxxx]
Sent: Friday, July 19, 2002 1:13 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  combining oracle node-set with msxml node-set



> This works fine in msxml

presumably that's the first case in your xsl:choose, once msxsl succeeds
on that it won't look at the other cases.

oracle though will correctly fall over the msxml namespace unless you
stop it looking

so you want
test="function-available('msxsl:node-test()') ...

of course by "depending on the processor" you may have meant that you do
have some such test in your xsl:choose (or use system-property) in which
case it might be a bug, can't be sure..

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list