BUG: XmlNamespaceManager Does Not Correctly Atomize Strings During Namespace Lookups (324996)
The information in this article applies to:
- Microsoft .NET Framework 1.0
- Microsoft .NET Framework 1.1
- Microsoft .NET Framework Class Libraries 1.0
- Microsoft .NET Framework Class Libraries 1.1
This article was previously published under Q324996 SYMPTOMS The LookupNamespace and LookupPrefix methods of the XmlNamespaceManager class may return a null value even when a matching namespace
definition has been added to the XmlNamespaceManager object. This problem is only noticed when you use the NameTable of an XmlDocument to construct the XmlNamespaceManager object instance. CAUSEXmlNamespaceManager does not correctly atomize strings while it executes namespace
lookups when the NameTable of an XmlDocument is used to construct the XmlNamespaceManager object and a string value is used to directly specify the
namespace prefix or URI to look up. RESOLUTION Use the Get method of the NameTable property of the XmlNamespaceManager object to supply the prefix and URI parameters when you execute
the LookupNamespace and LookupPrefix methods. Alternatively, you can supply a new NameTable object instance when you construct the XmlNamespaceManager object. STATUS Microsoft has confirmed that this is a bug in the
implementation of the XmlNamespaceManager class in the System.Xml Microsoft .NET Framework namespace.
Modification Type: | Major | Last Reviewed: | 9/18/2003 |
---|
Keywords: | kbbug kbpending KB324996 |
---|
|