Passing XML as XsltArgumentLis t, can't select children

[Tim Menninger]

I have seen the postings about passing XML into an XSL transformation. The
problem is that I cannot use any XPath navigation in the XSL that won't
generate an error. If I use <xsl:copy-of select="$var"/> then the XML is
output into the html page but this <xsl:copy-of select="$var/NS:Child"/>,
and all other XPath navigation, fails with the error that 'The expression
passed to this method should result in a NodeSet'. The real goal is to use
xsl:for-each to navigate over all $var's children but can't get it to work.

I have seen the samples and they all show I should be able to do this. The
only difference is that the samples never use namespaces and I have a
namspace on my xml.

Tim

[Oleg Tkachenko [MVP]]

Tim Menninger wrote:

I have seen the postings about passing XML into an XSL transformation. The
problem is that I cannot use any XPath navigation in the XSL that won't
generate an error. If I use <xsl:copy-of select="$var"/> then the XML is
output into the html page but this <xsl:copy-of select="$var/NS:Child"/>,
and all other XPath navigation, fails with the error that 'The expression
passed to this method should result in a NodeSet'. The real goal is to use
xsl:for-each to navigate over all $var's children but can't get it to work.

You must be passing XPathNavigator to XSLT?
You have to pass XPathNodeIterat or to be able to work with it as with
nodeset in XSLT.
XPathNavigator is RTF in XSLT, XPathNodeIterat or - nodeset.
--
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com

[Tim Menninger]

Oleg,

Thanks, I did try this but since my XML has a namespace I could not figure
out how to set the XsltContext for the query. Below is the code I am using.

//props is XmlNode
XPathNavigator nav = props.CreateNav igator();
XsltArgumentLis t args = new XsltArgumentLis t();
args.AddParam(" properties", "", nav.Select("/FE:Properties") );

The .Select() method throws an exception 'Namespace Manager or XsltContext
needed. This query has a prefix,
variable, or user-defined function'. The XmlNode's XmlDocument has the
correct context set, so props.SelectSin gleNode("/FE:Properties") does work.

I have tried to use the second param in AddParam but I do not think this
does what I need.

Tim
"Oleg Tkachenko [MVP]" <oleg@NO!SPAM!P LEASEtkachenko. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

Tim Menninger wrote:

I have seen the postings about passing XML into an XSL transformation. The problem is that I cannot use any XPath navigation in the XSL that won't
generate an error. If I use <xsl:copy-of select="$var"/> then the XML is
output into the html page but this <xsl:copy-of select="$var/NS:Child"/>, and all other XPath navigation, fails with the error that 'The expression passed to this method should result in a NodeSet'. The real goal is to use xsl:for-each to navigate over all $var's children but can't get it to

work.
You must be passing XPathNavigator to XSLT?
You have to pass XPathNodeIterat or to be able to work with it as with
nodeset in XSLT.
XPathNavigator is RTF in XSLT, XPathNodeIterat or - nodeset.
--
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com

[Tim Menninger]

Oleg thanks for the quick response,

I got it working but not really the way I wanted. If you could answer the
namespace question that would be great. This is what I changed

XPathNavigator nav = props.CreateNav igator();
XsltArgumentLis t args = new XsltArgumentLis t();
args.AddParam(" properties", "", nav.Select("./*")); //changed this to no
namespace XPath

Then used <xsl:for-each select="$proper ties"> to output rows

Thanks,

Tim

"Tim Menninger" <tm********@for ensicsexplorers .com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

Oleg,

Thanks, I did try this but since my XML has a namespace I could not figure
out how to set the XsltContext for the query. Below is the code I am using.
//props is XmlNode
XPathNavigator nav = props.CreateNav igator();
XsltArgumentLis t args = new XsltArgumentLis t();
args.AddParam(" properties", "", nav.Select("/FE:Properties") );

The .Select() method throws an exception 'Namespace Manager or XsltContext
needed. This query has a prefix,
variable, or user-defined function'. The XmlNode's XmlDocument has the
correct context set, so props.SelectSin gleNode("/FE:Properties") does work.
I have tried to use the second param in AddParam but I do not think this
does what I need.

Tim
"Oleg Tkachenko [MVP]" <oleg@NO!SPAM!P LEASEtkachenko. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

Tim Menninger wrote:

I have seen the postings about passing XML into an XSL transformation. The problem is that I cannot use any XPath navigation in the XSL that won't generate an error. If I use <xsl:copy-of select="$var"/> then the XML is output into the html page but this <xsl:copy-of select="$var/NS:Child"/>, and all other XPath navigation, fails with the error that 'The expression passed to this method should result in a NodeSet'. The real goal is to use xsl:for-each to navigate over all $var's children but can't get it to

work.

You must be passing XPathNavigator to XSLT?
You have to pass XPathNodeIterat or to be able to work with it as with
nodeset in XSLT.
XPathNavigator is RTF in XSLT, XPathNodeIterat or - nodeset.
--
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com

[Oleg Tkachenko [MVP]]

Tim Menninger wrote:

args.AddParam(" properties", "", nav.Select("/FE:Properties") );

The .Select() method throws an exception 'Namespace Manager or XsltContext
needed. This query has a prefix,
variable, or user-defined function'. The XmlNode's XmlDocument has the
correct context set, so props.SelectSin gleNode("/FE:Properties") does work.

You have to provide XmlNamespaceMan ager to Select method to define FE
prefix:

XPathExpression expr = nav.Compile("/FE:Properties") ;
XmlNamespaceMan ager mngr = new XmlNamespaceMan ager(nav.NameTa ble);
mngr.AddNamespa ce("FE","FE namespace URI goes here");
expr.SetContext (mngr);
args.AddParam(" properties", "", nav.Select(expr ));

--
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com

[Tim Menninger]

Oleg,

Thanks, got it working. I had tried this but I was using the prop's
XmlDocument NameTable not the nav's NameTable this must have caused a
problem. I actually have a wrapper class around XmlDocument that manages my
namespaces so I don't have to create a namespace manager for each dom. I was
using my GetNsMgr() accessor to return the XmlDocuments namespace manage and
pass that to SetContext but that didn't work. When you recreate a namespace
manager it works.

Thanks,

Tim
"Oleg Tkachenko [MVP]" <oleg@NO!SPAM!P LEASEtkachenko. com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

Tim Menninger wrote:

args.AddParam(" properties", "", nav.Select("/FE:Properties") );

The .Select() method throws an exception 'Namespace Manager or XsltContext needed. This query has a prefix,
variable, or user-defined function'. The XmlNode's XmlDocument has the
correct context set, so props.SelectSin gleNode("/FE:Properties") does

work.
You have to provide XmlNamespaceMan ager to Select method to define FE
prefix:

XPathExpression expr = nav.Compile("/FE:Properties") ;
XmlNamespaceMan ager mngr = new XmlNamespaceMan ager(nav.NameTa ble);
mngr.AddNamespa ce("FE","FE namespace URI goes here");
expr.SetContext (mngr);
args.AddParam(" properties", "", nav.Select(expr ));

--
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com