INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 2 (Part 2 of 4)

This article is part 2 of 4 in the series of articles documenting the bugs fixed in MSXML 3.0 Service Pack 2 (MSXML 3.0 SP2).


For additional information about MSXML 3.0 SP2, click the article numbers below to view the articles in the Microsoft Knowledge Base:

BUG: WHERE clause in selectNodes arguments does not process multiple nodes

When you execute the MSXML Document Object Model (DOM) selectNodes method to identify occurrences of a specified node in an XML document based on the attribute value of a parent node, and you specify a conditional query expression, the multiple matching nodes that exist in the document may not be returned. You can observe this behavior when multiple instances of the specified parent node exist in the XML data for a single occurrence of the target node, and the instances are not listed in ascending order by the attribute that is specified in the query expression.

BUG: MXXMLWriter threading problem

The MSXML2.MXXMLWriter object cannot be used in multi-threaded apartments because its threading model is registered as being Apartment threaded.

BUG: Having template match to /node() causes GPF in Internet Explorer

When you set the expression of the match attribute of an xsl:template element in an XSLT document to /node(), a GPF occurs in Internet Explorer.

BUG: Extra default namespace declarations produced on children of a node that contains a default namespace declaration

An additional default namespace declaration attribute of the form xmlns="" is appended to nodes in an XML document that is loaded or accessed by using the MSXML DOM. The additional default namespace declaration is seen in nodes whose parent node has a default namespace declaration attribute.