Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=79047 --- shadow/79047 2006-08-10 04:00:40.000000000 -0400 +++ shadow/79047.tmp.13608 2006-08-10 09:46:34.000000000 -0400 @@ -146,6 +146,34 @@ to opening/closing elements and it seems to behave correctly. The next suspect I guess would be whatever class is calling XmlTextWriter - could you point me in the right direction? I had a poke through the S.Web.Services source directory but could not pinpoint what is calling XmlTextWriter. + +------- Additional Comments From [EMAIL PROTECTED] 2006-08-10 09:46 ------- +This seems to be a bug in XmlNamespaceManager.AddNamespace() + + public virtual void AddNamespace (string prefix, string uri) + { + AddNamespace (prefix, uri, false); + } + + +Compare to LookupNamespace: + public virtual string LookupNamespace (string prefix) + { +#if NET_2_0 + return LookupNamespace (prefix, false); +#else + return LookupNamespace (prefix, true); +#endif + } + + +So, the namespace is added with atomizedNames disabled; and then +looked up with it enabled - resulting in the q1 namespace not being +located. + +Changing AddNamespace() to use the same pattern as LookupNamespace() +seems to correct the problem. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
