|
|
 next
|
  Subject: Error when generating .NET code for pipeline
Author: Rodolfo Vegas
Date: 30 Jan 2008 10:48 AM
|
Hi Ivan, thanks for your quick response.
I have to make a correction regarding my first post: the pipeline executes well, but with Saxonica Saxon execution framework. With Microsoft .NET execution framework selected (with both .NET XslTransform and XslCompiledTransform XSLT processors selected) it reports the following error:
"System.Xml.XPath.XPathException: Namespace Manager or XsltContext needed. This query has a prefix, variable, or user-defined function.
at MS.Internal.Xml.XPath.CompiledXpathExpr.get_QueryTree()
at System.Xml.XPath.XPathNavigator.Evaluate(XPathExpression expr, XPathNodeIterator context)
at System.Xml.XPath.XPathNavigator.Evaluate(String xpath)
at __process(Char* xmlFileName, Char* xsltFileName, IMSXMLDriver* pDriver)
Error: XSLT processing by XSLT node 'Fusión de ficheros' failed: System.Xml.XPath.XPathException: Namespace Manager or XsltContext needed. This query has a prefix, variable, or user-defined function.
at MS.Internal.Xml.XPath.CompiledXpathExpr.get_QueryTree()
at System.Xml.XPath.XPathNavigator.Evaluate(XPathExpression expr, XPathNodeIterator context)
at System.Xml.XPath.XPathNavigator.Evaluate(String xpath)
at __process(Char* xmlFileName, Char* xsltFileName, IMSXMLDriver* pDriver)"
The XSLT node called 'Fusión de ficheros' is the last one, which has to merge the 8 XML files into the one only final XML.
I wonder if it has something to do with the fact that I use a global variable for each of the 8 files, and also have one of these files as the source XML declared in the Scenario properties of the XSLT file. So I have 9 input ports for the XSLT node, and, although the match attribute for the template is set to "/", mapping the root node of this last file (if I'm right), all the data used in the template are related to the files being pointed to by the global variables.
To me (but I'm just a begginer in the XML world), the message seems to indicate that the XSLT processor is not able to get/construct a node-tree to apply the transformation on, maybe due to the fact that I don't explicitly use any data of the XML file the input port is pointing to.
One question about this: Isn't there any way of suppressing this input port? (not needed in my case, as that file is referenced by one of the 8 global variables).
On another way: Do you really need me to send you all the files? 8 XML original source files, 8 XML transformed 'output' files, 1 final XML file, 9 XSLT files and 1 pipeline file (27 in total if I don't forget any).
Rgds,
Rodolfo
|
|
|
|
|
top