![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >microsoft.public.xsl Archive Home >Recent entries >Thread Prev - Re: Passing an XPathNavigator to a custum function. >Thread Next - Re: Passing an XPathNavigator to a custum function. Re: Passing an XPathNavigator to a custum function.To: NULL Date: 8/2/2008 10:39:00 AM Not to be argumentative but mearly trying to understand. Besides, whatever works, right? There is some sample code under the XPathNavigator that shows recursive calls to XPathNavigator using MoveNext() starting out with MoveToFirstChild(). This would suggest that XPathNavigator handles more than one node. If not then what is the difference between XPathNavigator and just XmlNode? Thanks again. "Martin Honnen" wrote: > Kevin Burton wrote: > > > <msxsl:script language="C#" implements-prefix="bsi"> > > public bool MerchandisedProduct(string connectionString, XPathNavigator nav) > > { > > return false; > > } > > </msxsl:script> > > > not(bsi:MerchandisedProduct($CatalogConnectionString,Relationship/Relation/SKU))])"/> > > > I was wondering if this is a limitation of Xslt or if there was a work around? > > I think the problem is the extension function, you have defined the > second argument as an XPathNavigator but then you pass in a node-set > with several arguments (Relationship/Relation/SKU), that does not work. > You need to use an XPathNodeIterator as the argument type if you want to > pass in a node-set with several nodes. If you want to use the type > XPathNavigator then you need to make sure you pass in a single node. > > > -- > > Martin Honnen --- MVP XML > http://JavaScript.FAQTs.com/ > | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||
|
