Sorry, I don't know how to describe the issue further. What information are
you looking for?
I have a .Net object I pass in as an URN with defined XSLT extensions and
then they are called from the style sheet. I create the node as outlined in
the original problem and execute the user function as shown in the sample.
[quoted text, click to view] "Dimitre Novatchev" <dimitren@tpg.com.au> wrote in message
news:4362f860$0$21067$892e7fe2@authen.white.readfreenews.net...
Too little information is provided to engage in an answer...
Cheers,
Dimitre Novatchev
[quoted text, click to view] "Matt" <mdframe@sorvive.DONT-SEND-SPAM.com> wrote in message
news:%23XVvIfB3FHA.744@TK2MSFTNGP10.phx.gbl...
I need help with passing a generated node set from a style sheet into my
customer msxsl extension. I have the following node set that I am creating:
<xsl:variable name="sql">
<SQL>
<StoredProc>spGetReconID</StoredProc>
<Parms>
<parm>
<name>@tran</name>
<value>956</value>
</parm>
<parm>
<name>@refnbr</name>
<value><xsl:value-of select="$shipnbr"/></value>
</parm>
<parm>
<name>@keyfld</name>
<value><xsl:value-of select="$ponbr"/></value>
</parm>
</Parms>
</SQL>
</xsl:variable>
<xsl:value-of select="user:GetDBValue('myDB', msxsl:node-set($sql))"/>
The return value is just a string as we only want to return a single
value. The above code is inside a template and that is why we execute the
user function with only a value-of statement. We are trying to create a
generic type function that is why we are trying to use the node-set to allow
future flexibility. When we receive the node-set in the extended function
we only see the XML that was passed to the style sheet and not the above
node-set. Does anyonen have a sample they can share on how to get this
working?
Thanks,
Matt