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

Article translations Article translations
Article ID: 308563 - View products that this article applies to.
This article was previously published under Q308563
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SUMMARY


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

The following bugs have been fixed in MSXML 3.0 SP2:
For additional information about MSXML 3.0 SP2, click the article number below to view the article in the Microsoft Knowledge Base:
308480 INFO: How to Obtain the Latest Microsoft XML 3.0 Service Pack

MORE INFORMATION

BUG: XPath search fails when you search into external parsed entities

If the Test.xml file contains the following XML data
<!DOCTYPE RootElement[
       <!ELEMENT RootElement (ExternalElement) >
       <!ELEMENT ExternalElement (#PCDATA) >
       <!ENTITY External SYSTEM 'external.xml'>]>
<RootElement> &External; </RootElement>
				
that contains a reference to another XML file, External.xml, as follows
<ExternalElement>Inner Text of External Element</ExternalElement>
				
and calls the following:
xmldoc.documentElement.selectSingleNode(  "ExternalElement"  )
				
no node is returned with the MSXML 3.0 parser.



BUG: Doc stream does not parse XML until the stream is closed

When you call QueryInterface on the DOMDocument object for an IStream interface and then write to the stream, the DOMDocument is not loaded until the stream is released. You expect the parser to be invoked when you call IStream::Commit.



BUG: XPath function generates duplicate IDs for namespace nodes and default attributes

The XPath generate-id function returns duplicate node IDs for namespace nodes and default attributes.

For example, the XSL transformation generates output that contains duplicate IDs when you apply the following style sheet
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
  <xsl:output method="text" encoding="UTF-8"/>
  <xsl:template match="/">
    <xsl:for-each select="//*/namespace::*" xmlns:a="urn:sample">
      <xsl:text>Element </xsl:text>
      <xsl:value-of select="name(parent::*)"/>
      <xsl:text>, id of namespace </xsl:text>
      <xsl:value-of select="name(.)"/>
      <xsl:text> = </xsl:text>
      <xsl:value-of select="generate-id(.)"/>
      <xsl:text>&#xa;</xsl:text>
    </xsl:for-each>
  </xsl:template>
</xsl:stylesheet>
				
to the following XML data:
<a:a xmlns:a="urn:sample">
  <a:b>
    <a:c/>
  </a:b>
</a:a>
				


BUG: MSXML may fail to report encoding errors when you save small XML files

When you save a small XML file that contains characters that are not supported by a given encoding, MSXML 3.0 and 3.0 SP1 may fail to report the encoding errors. Starting with MSXML 3.0 SP2, the encoding errors are always reported.

REFERENCES

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

Properties

Article ID: 308563 - Last Review: February 27, 2014 - Revision: 1.1
APPLIES TO
  • Microsoft XML Parser 3.0
  • Microsoft XML Parser 3.0 Service Pack 1
  • Microsoft XML Parser 3.0 Service Pack 2
Keywords: 
kbnosurvey kbarchive kbbug kbinfo KB308563

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com