![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >microsoft.public.xsl Archive Home >Recent entries >Thread Prev - Re: node-set($variable) just won't allow any results - what do I need to change? >Thread Next - Re: node-set($variable) just won't allow any results - what do I need to change? Re: node-set($variable) just won't allow any results - what do I need to change?To: NULL Date: 7/6/2007 11:51:00 AM On Jul 6, 8:12 am, Martin Honnen <mahotr...@yahoo.de> wrote: > ParanoidMike wrote: > > I'm sure I *do* misunderstand. Do you have any suggestions for how I > > could achieve what I want within the existing environment? > > It might work to simply use XPath expression alike > /ThreatModel/Threats/*[local-name() = concat($ThreatCategory, > 's')]/Threats/*[local-name() = $ThreatCategory] > that way you are not able to dynamically evaluate XPath expressions in > general but for a limited set the check *[local-name() = $someVariable] > might suffice. > > Martin Honnen --- MVP XML > http://JavaScript.FAQTs.com/ Thank you. And in case there's still room for misunderstanding: if "$ThreatXPath is not a result tree fragment, it is a string with an XPath expression", is there some way I can rewrite my code to turn $ThreatXPath into an RTF, so the node-set() I thought I was able to achieve would work? Or is the use of the local-name() function the closest I'd ever get? Thanks again! Mike | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
