Bug in MSXML / XML Parser .Net

[Michael]

Hi,

I have a problem parsing XML file using XSLT stylesheet by using :

using System.Xml;
using System.Xml.XPat h;
using System.Xml.Xsl;

// load Xsl stylesheet
XslTransform myXslTrans = new XslTransform() ;
myXslTrans.Load (Server.MapPath ("stylesheet.xs lt"));

// load the Xml doc
XPathDocument myXPathDoc = new XPathDocument(S erver.MapPath(" file.xml"));

// write the transformed result
XmlTextWriter writer = new XmlTextWriter(S erver.MapPath(" result.xml"), null);

// do the actual transform of Xml
// pass XmlResolver to Transform() method
myXslTrans.Tran sform(myXPathDo c, null, writer, null);
writer.Close();
XML file

<?xml version="1.0" encoding="utf-8"?>

<Documents>
<Document chapter="1" title="title 1" href="file1.xml " filter="">
<Article title="1.1" info="sub" filter="food"/>
<Article title="1.2" info="main" filter="food"/>
</Document>
<Document chapter="2" title="title 2" href="file2.xml " filter="drink">
<Article title="2.1" info="sub" filter="drink"/>
<Article title="2.2" info="main" filter="food"/>
</Document>
</Documents>
XSLT stylesheet

<?xml version='1.0' encoding='UTF-8'?>

<xsl:styleshe et version="1.0"
xmlns:xsl="http ://www.w3.org/1999/XSL/Transform">

<!-- using muenchian method group by an attribute by asigning a unique
key to each element -->

<xsl:output method="html" version="1.0" encoding="UTF-8" indent="yes"/>

<!-- xsl:key name="by-proctype" match="Doc" use="@procedure type"/ -->

<!-- define info key -->
<xsl:key name="by-info" match="Article" use="@info"/>

<!-- put the filter string in a global parameter -->
<xsl:param name="filter" select="'food'"/>

<xsl:template match="Document s"><!-- @filter='' will be true if it is
there and empty or if it is not there at all) -->

<documents>
<xsl:for-each select="Documen t[@filter='' or
@filter=$filter]/Article[count(.|key('by-info',@info)[@filter='' or
@filter=$filter][1])=1]">
<document name="{@info}"> <xsl:copy-of
select="key('by-info',@info)[@filter=$filter]"/></document>
</xsl:for-each>
</documents>
</xsl:template>

</xsl:stylesheet>
Exception Details:

System.NullRefe renceException: Object reference not set to an instance of an
object."

Stack Trace:

[NullReferenceEx ception: Object reference not set to an instance of an
object.]
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.MergeFilterQu ery.SetXsltCont ext(XsltContext input)
System.Xml.XPat h.OrQuery.SetXs ltContext(XsltC ontext context)
System.Xml.XPat h.MethodOperand .SetXsltContext (XsltContext context)
System.Xml.XPat h.LogicalExpr.S etXsltContext(X sltContext context)
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.MergeFilterQu ery.SetXsltCont ext(XsltContext input)
System.Xml.XPat h.CompiledXpath Expr.SetContext (XmlNamespaceMa nager
nsManager)
System.Xml.Xsl. Processor.GetCo mpiledQuery(Int 32 key)
System.Xml.Xsl. Processor.Start Query(XPathNavi gator context, Int32 key)
System.Xml.Xsl. ForEachAction.E xecute(Processo r processor, ActionFrame
frame)
System.Xml.Xsl. ActionFrame.Exe cute(Processor processor)
System.Xml.Xsl. Processor.Execu te()
System.Xml.Xsl. XslTransform.Tr ansform(XPathNa vigator input,
XsltArgumentLis t args, XmlWriter output, XmlResolver resolver)
System.Xml.Xsl. XslTransform.Tr ansform(IXPathN avigable input,
XsltArgumentLis t args, XmlWriter output, XmlResolver resolver)
com.pop.mm_main _v2.Page_Load(O bject sender, EventArgs e) in
c:\inetpub\wwwr oot\file\index. aspx.cs:61
......
When I use XMLSpy to parse the XML using MSXML 4 processor it works perfect.
Saxon works perfectly as well. But when I try to parse it trough C#, I get
the error above.

It looks like I don't use MSXML 4 at all.

How do I make sure that MSXML 4 is used when I parse?

Thank you,

-Mike

[Michael]

I have figured out that this is a parser issue.
My IE is using version 3.0 set as default in registry.

http://www.perfectxml.com/articles/xml/XSLTInMSXML.asp

There must be a way to set this in a namespace so, IE does understand what
processor to use.

/Michael

"Michael" wrote:

Hi,

I have a problem parsing XML file using XSLT stylesheet by using :

using System.Xml;
using System.Xml.XPat h;
using System.Xml.Xsl;

// load Xsl stylesheet
XslTransform myXslTrans = new XslTransform() ;
myXslTrans.Load (Server.MapPath ("stylesheet.xs lt"));

// load the Xml doc
XPathDocument myXPathDoc = new XPathDocument(S erver.MapPath(" file.xml"));

// write the transformed result
XmlTextWriter writer = new XmlTextWriter(S erver.MapPath(" result.xml"), null);

// do the actual transform of Xml
// pass XmlResolver to Transform() method
myXslTrans.Tran sform(myXPathDo c, null, writer, null);
writer.Close();
XML file

<?xml version="1.0" encoding="utf-8"?>

<Documents>
<Document chapter="1" title="title 1" href="file1.xml " filter="">
<Article title="1.1" info="sub" filter="food"/>
<Article title="1.2" info="main" filter="food"/>
</Document>
<Document chapter="2" title="title 2" href="file2.xml " filter="drink">
<Article title="2.1" info="sub" filter="drink"/>
<Article title="2.2" info="main" filter="food"/>
</Document>
</Documents>
XSLT stylesheet

<?xml version='1.0' encoding='UTF-8'?>

<xsl:styleshe et version="1.0"
xmlns:xsl="http ://www.w3.org/1999/XSL/Transform">

<!-- using muenchian method group by an attribute by asigning a unique
key to each element -->

<xsl:output method="html" version="1.0" encoding="UTF-8" indent="yes"/>

<!-- xsl:key name="by-proctype" match="Doc" use="@procedure type"/ -->

<!-- define info key -->
<xsl:key name="by-info" match="Article" use="@info"/>

<!-- put the filter string in a global parameter -->
<xsl:param name="filter" select="'food'"/>

<xsl:template match="Document s"><!-- @filter='' will be true if it is
there and empty or if it is not there at all) -->

<documents>
<xsl:for-each select="Documen t[@filter='' or
@filter=$filter]/Article[count(.|key('by-info',@info)[@filter='' or
@filter=$filter][1])=1]">
<document name="{@info}"> <xsl:copy-of
select="key('by-info',@info)[@filter=$filter]"/></document>
</xsl:for-each>
</documents>
</xsl:template>

</xsl:stylesheet>
Exception Details:

System.NullRefe renceException: Object reference not set to an instance of an
object."

Stack Trace:

[NullReferenceEx ception: Object reference not set to an instance of an
object.]
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.MergeFilterQu ery.SetXsltCont ext(XsltContext input)
System.Xml.XPat h.OrQuery.SetXs ltContext(XsltC ontext context)
System.Xml.XPat h.MethodOperand .SetXsltContext (XsltContext context)
System.Xml.XPat h.LogicalExpr.S etXsltContext(X sltContext context)
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.MergeFilterQu ery.SetXsltCont ext(XsltContext input)
System.Xml.XPat h.CompiledXpath Expr.SetContext (XmlNamespaceMa nager
nsManager)
System.Xml.Xsl. Processor.GetCo mpiledQuery(Int 32 key)
System.Xml.Xsl. Processor.Start Query(XPathNavi gator context, Int32 key)
System.Xml.Xsl. ForEachAction.E xecute(Processo r processor, ActionFrame
frame)
System.Xml.Xsl. ActionFrame.Exe cute(Processor processor)
System.Xml.Xsl. Processor.Execu te()
System.Xml.Xsl. XslTransform.Tr ansform(XPathNa vigator input,
XsltArgumentLis t args, XmlWriter output, XmlResolver resolver)
System.Xml.Xsl. XslTransform.Tr ansform(IXPathN avigable input,
XsltArgumentLis t args, XmlWriter output, XmlResolver resolver)
com.pop.mm_main _v2.Page_Load(O bject sender, EventArgs e) in
c:\inetpub\wwwr oot\file\index. aspx.cs:61
.....
When I use XMLSpy to parse the XML using MSXML 4 processor it works perfect.
Saxon works perfectly as well. But when I try to parse it trough C#, I get
the error above.

It looks like I don't use MSXML 4 at all.

How do I make sure that MSXML 4 is used when I parse?

Thank you,

-Mike

[Michael]

As a workaround I used generate-id() function in Muenchian method instead of
count():
Something with numeric predicate I think.

<xsl:for-each select="Documen t[@filter='' or
@filter=$filter]/Article[generate-id()=generate-id(key('by-info',@info)[@filter='' or @filter=$filter])]">

Now it works as it should.

--Michael

"Michael" wrote:

I have figured out that this is a parser issue.
My IE is using version 3.0 set as default in registry.

http://www.perfectxml.com/articles/xml/XSLTInMSXML.asp

There must be a way to set this in a namespace so, IE does understand what
processor to use.

/Michael

"Michael" wrote:

Hi,

I have a problem parsing XML file using XSLT stylesheet by using :

using System.Xml;
using System.Xml.XPat h;
using System.Xml.Xsl;

// load Xsl stylesheet
XslTransform myXslTrans = new XslTransform() ;
myXslTrans.Load (Server.MapPath ("stylesheet.xs lt"));

// load the Xml doc
XPathDocument myXPathDoc = new XPathDocument(S erver.MapPath(" file.xml"));

// write the transformed result
XmlTextWriter writer = new XmlTextWriter(S erver.MapPath(" result.xml"), null);

// do the actual transform of Xml
// pass XmlResolver to Transform() method
myXslTrans.Tran sform(myXPathDo c, null, writer, null);
writer.Close();
XML file

<?xml version="1.0" encoding="utf-8"?>

<Documents>
<Document chapter="1" title="title 1" href="file1.xml " filter="">
<Article title="1.1" info="sub" filter="food"/>
<Article title="1.2" info="main" filter="food"/>
</Document>
<Document chapter="2" title="title 2" href="file2.xml " filter="drink">
<Article title="2.1" info="sub" filter="drink"/>
<Article title="2.2" info="main" filter="food"/>
</Document>
</Documents>
XSLT stylesheet

<?xml version='1.0' encoding='UTF-8'?>

<xsl:styleshe et version="1.0"
xmlns:xsl="http ://www.w3.org/1999/XSL/Transform">

<!-- using muenchian method group by an attribute by asigning a unique
key to each element -->

<xsl:output method="html" version="1.0" encoding="UTF-8" indent="yes"/>

<!-- xsl:key name="by-proctype" match="Doc" use="@procedure type"/ -->

<!-- define info key -->
<xsl:key name="by-info" match="Article" use="@info"/>

<!-- put the filter string in a global parameter -->
<xsl:param name="filter" select="'food'"/>

<xsl:template match="Document s"><!-- @filter='' will be true if it is
there and empty or if it is not there at all) -->

<documents>
<xsl:for-each select="Documen t[@filter='' or
@filter=$filter]/Article[count(.|key('by-info',@info)[@filter='' or
@filter=$filter][1])=1]">
<document name="{@info}"> <xsl:copy-of
select="key('by-info',@info)[@filter=$filter]"/></document>
</xsl:for-each>
</documents>
</xsl:template>

</xsl:stylesheet>
Exception Details:

System.NullRefe renceException: Object reference not set to an instance of an
object."

Stack Trace:

[NullReferenceEx ception: Object reference not set to an instance of an
object.]
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.MergeFilterQu ery.SetXsltCont ext(XsltContext input)
System.Xml.XPat h.OrQuery.SetXs ltContext(XsltC ontext context)
System.Xml.XPat h.MethodOperand .SetXsltContext (XsltContext context)
System.Xml.XPat h.LogicalExpr.S etXsltContext(X sltContext context)
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.MergeFilterQu ery.SetXsltCont ext(XsltContext input)
System.Xml.XPat h.CompiledXpath Expr.SetContext (XmlNamespaceMa nager
nsManager)
System.Xml.Xsl. Processor.GetCo mpiledQuery(Int 32 key)
System.Xml.Xsl. Processor.Start Query(XPathNavi gator context, Int32 key)
System.Xml.Xsl. ForEachAction.E xecute(Processo r processor, ActionFrame
frame)
System.Xml.Xsl. ActionFrame.Exe cute(Processor processor)
System.Xml.Xsl. Processor.Execu te()
System.Xml.Xsl. XslTransform.Tr ansform(XPathNa vigator input,
XsltArgumentLis t args, XmlWriter output, XmlResolver resolver)
System.Xml.Xsl. XslTransform.Tr ansform(IXPathN avigable input,
XsltArgumentLis t args, XmlWriter output, XmlResolver resolver)
com.pop.mm_main _v2.Page_Load(O bject sender, EventArgs e) in
c:\inetpub\wwwr oot\file\index. aspx.cs:61
.....
When I use XMLSpy to parse the XML using MSXML 4 processor it works perfect.
Saxon works perfectly as well. But when I try to parse it trough C#, I get
the error above.

It looks like I don't use MSXML 4 at all.

How do I make sure that MSXML 4 is used when I parse?

Thank you,

-Mike

[Michael]

Hello,

This looks like a Bug! How can this be reported to Microsoft to appropriate
developer team?

Something with numeric predicate I think.
As a workaround you can use generate-id() function in Muenchian method
instead of count():

<xsl:for-each select="Documen t[@filter='' or
@filter=$filter]/Article[generate-id()=generate-id(key('by-info',@info)[@filter='' or @filter=$filter])]">

-Michael
"Michael" wrote:

I have figured out that this is a parser issue.
My IE is using version 3.0 set as default in registry.

http://www.perfectxml.com/articles/xml/XSLTInMSXML.asp

There must be a way to set this in a namespace so, IE does understand what
processor to use.

/Michael

"Michael" wrote:

Hi,

I have a problem parsing XML file using XSLT stylesheet by using :

using System.Xml;
using System.Xml.XPat h;
using System.Xml.Xsl;

// load Xsl stylesheet
XslTransform myXslTrans = new XslTransform() ;
myXslTrans.Load (Server.MapPath ("stylesheet.xs lt"));

// load the Xml doc
XPathDocument myXPathDoc = new XPathDocument(S erver.MapPath(" file.xml"));

// write the transformed result
XmlTextWriter writer = new XmlTextWriter(S erver.MapPath(" result.xml"), null);

// do the actual transform of Xml
// pass XmlResolver to Transform() method
myXslTrans.Tran sform(myXPathDo c, null, writer, null);
writer.Close();
XML file

<?xml version="1.0" encoding="utf-8"?>

<Documents>
<Document chapter="1" title="title 1" href="file1.xml " filter="">
<Article title="1.1" info="sub" filter="food"/>
<Article title="1.2" info="main" filter="food"/>
</Document>
<Document chapter="2" title="title 2" href="file2.xml " filter="drink">
<Article title="2.1" info="sub" filter="drink"/>
<Article title="2.2" info="main" filter="food"/>
</Document>
</Documents>
XSLT stylesheet

<?xml version='1.0' encoding='UTF-8'?>

<xsl:styleshe et version="1.0"
xmlns:xsl="http ://www.w3.org/1999/XSL/Transform">

<!-- using muenchian method group by an attribute by asigning a unique
key to each element -->

<xsl:output method="html" version="1.0" encoding="UTF-8" indent="yes"/>

<!-- xsl:key name="by-proctype" match="Doc" use="@procedure type"/ -->

<!-- define info key -->
<xsl:key name="by-info" match="Article" use="@info"/>

<!-- put the filter string in a global parameter -->
<xsl:param name="filter" select="'food'"/>

<xsl:template match="Document s"><!-- @filter='' will be true if it is
there and empty or if it is not there at all) -->

<documents>
<xsl:for-each select="Documen t[@filter='' or
@filter=$filter]/Article[count(.|key('by-info',@info)[@filter='' or
@filter=$filter][1])=1]">
<document name="{@info}"> <xsl:copy-of
select="key('by-info',@info)[@filter=$filter]"/></document>
</xsl:for-each>
</documents>
</xsl:template>

</xsl:stylesheet>
Exception Details:

System.NullRefe renceException: Object reference not set to an instance of an
object."

Stack Trace:

[NullReferenceEx ception: Object reference not set to an instance of an
object.]
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.MergeFilterQu ery.SetXsltCont ext(XsltContext input)
System.Xml.XPat h.OrQuery.SetXs ltContext(XsltC ontext context)
System.Xml.XPat h.MethodOperand .SetXsltContext (XsltContext context)
System.Xml.XPat h.LogicalExpr.S etXsltContext(X sltContext context)
System.Xml.XPat h.FilterQuery.S etXsltContext(X sltContext input)
System.Xml.XPat h.MergeFilterQu ery.SetXsltCont ext(XsltContext input)
System.Xml.XPat h.CompiledXpath Expr.SetContext (XmlNamespaceMa nager
nsManager)
System.Xml.Xsl. Processor.GetCo mpiledQuery(Int 32 key)
System.Xml.Xsl. Processor.Start Query(XPathNavi gator context, Int32 key)
System.Xml.Xsl. ForEachAction.E xecute(Processo r processor, ActionFrame
frame)
System.Xml.Xsl. ActionFrame.Exe cute(Processor processor)
System.Xml.Xsl. Processor.Execu te()
System.Xml.Xsl. XslTransform.Tr ansform(XPathNa vigator input,
XsltArgumentLis t args, XmlWriter output, XmlResolver resolver)
System.Xml.Xsl. XslTransform.Tr ansform(IXPathN avigable input,
XsltArgumentLis t args, XmlWriter output, XmlResolver resolver)
com.pop.mm_main _v2.Page_Load(O bject sender, EventArgs e) in
c:\inetpub\wwwr oot\file\index. aspx.cs:61
.....
When I use XMLSpy to parse the XML using MSXML 4 processor it works perfect.
Saxon works perfectly as well. But when I try to parse it trough C#, I get
the error above.

It looks like I don't use MSXML 4 at all.

How do I make sure that MSXML 4 is used when I parse?

Thank you,

-Mike

[Oleg Tkachenko [MVP]]

Michael wrote:

I have figured out that this is a parser issue.
My IE is using version 3.0 set as default in registry.

IE always using MSXML3. The on;y way to use MSXML4 is scripting.

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

[mattmat]

I do not manage to add new message to the list (I must choose a discussion
group but the list is empty !) so I put my post hier as reply... It's also a
kind of MSXSL bug.

I'd just like to spécify a probable "exeption" in SelectSingleNod e() method.
The spec says :
"var objXMLDOMNode = oXMLDOMNode.sel ectSingleNode(q ueryString);
Where queryString is a string specifying an XPath expression."

But if you for example aim at matching the SECOND <foo> node of a context
node, you must write selectSingleNod e(foo[1])
the FIRST one is selectSingleNod e(foo[0])

Normaly, Xpath index position start at 1 (foo[1] is the short for
foo[position()=1]) :
<xsl:value-of select="foo[1]"> will match the FISRT foo node in XSL.

About the SelectSingleNod e() spec queryString is not a real XPath
expression, because of this exeption (maybe there are others ?), isn't it ?

[mattmat]

I did not manage to add a new message (I shall choose a discussion group but
the list is empty !) so I send it here as reply since it's also a kind of
Msxsml bug...

I'd just like to spécify a probable "exeption" in SelectSingleNod e() method.
The spec says :
"var objXMLDOMNode = oXMLDOMNode.sel ectSingleNode(q ueryString);
Where queryString is a string specifying an XPath expression."

But if you for example aim at matching the SECOND <foo> node of a context
node, you must write selectSingleNod e(foo[1])
the FIRST one is selectSingleNod e(foo[0])

Normaly, Xpath index position start at 1 (foo[1] is the short for
foo[position()=1]) :
<xsl:value-of select="foo[1]"> will match the FISRT foo node in XSL.

About the SelectSingleNod e() spec queryString is not a real XPath
expression, because of this exeption (maybe there are others ?), isn't it ?

[Oleg Tkachenko [MVP]]

mattmat wrote:

I'd just like to spécify a probable "exeption" in SelectSingleNod e() method.
The spec says :
"var objXMLDOMNode = oXMLDOMNode.sel ectSingleNode(q ueryString);
Where queryString is a string specifying an XPath expression."

But if you for example aim at matching the SECOND <foo> node of a context
node, you must write selectSingleNod e(foo[1])
the FIRST one is selectSingleNod e(foo[0])

Well, chances are you are using MSXML3, where selection language by
default isn't XPath, but some obsoleted language called XSL Pattern. I
have no idea which number position starts in that language.
Set XPath as selection language using SelectionLangua ge property.

PS. And it has nothing to do with .NET of course.
--
Oleg Tkachenko [XML MVP]
http://blog.tkachenko.com