Possible Bug : HttpPost and class name conflicts

[Edmund Green]

Included below is a minimal web-service implementation to recreate a problem
I've encountered in a web service that has methods returning classes with the
same local name (but in different namespaces).

If only the SoapHttp protocol is enabled in the web.config, everything works
as expected - with the different "Something" classes being serialized in to
different XML namespaces as defined by the ResponseNamespa ce property of the
SoapDocumentMet hod attributes.

However - if HttpPost or HttpPostLocalho st are enabled (the latter being
enabled by default), and I browse to the asmx file in IE, I get this error :

Types NsProblem.B.Som ething and NsProblem.A.Som ething both use the XML type
name, Something, from namespace http://example/NsProblem/. Use XML attributes
to specify a unique XML name and/or namespace for the type.

If I un-comment both of the "XmlRoot" elements I get this error

The XML element named 'Something' from namespace 'http://example/NsProblem/'
references distinct types NsProblem.A.Som ething and NsProblem.B.Som ething.
Use XML attributes to specify another XML name or namespace for the element
or types.

Now for the really strange bit : leave one XmlRoot attribute commented, and
the other not, and it works!

When it is working, the example responses (on whatever.asmx?o p=GetArrayA)
don't appear to tbe any difference!

(aside: I also tried setting the responses to be different using Xml
Serialization attributes, i.e. putting [return: XmlElement(... )] on the
methods, but like the SoapDocumentMet hod attribute this only seemed to change
the response for the Soap method - making no difference to the HTTP POST
response)

Various workarounds are available
- disable (remove) "HttpPost" and "HttpPostLocalh ost" in web.config
- Rename the classes (making the namespaces redundant)
but I would prefer to be able to keep the class names as they are, and keep
the HttpPostLocalho st enabled for testing / debugging purposes - and I
anticipate needing to support 3 or more classes with the same local-name
across different namespaces.

Edmund Green.
http://www.greenius.ltd.uk/

---- Minimal test case ----

<%@ WebService Language="c#" Class="NsProble m.XmlTestSvc" %>
using System;
using System.Web.Serv ices;
using System.Web.Serv ices.Protocols;
using System.Xml.Seri alization;

namespace NsProblem.A
{
// [XmlRoot(Namespa ce="AAAA")]
public class Something { }
}

namespace NsProblem.B
{
// [XmlRoot(Namespa ce="BBBB")]
public class Something { }
}

namespace NsProblem
{
[WebService(Desc ription="Confli cting name problem example",
Namespace="http ://example/NsProblem/")]
public class XmlTestSvc : System.Web.Serv ices.WebService
{
[WebMethod]
[SoapDocumentMet hod(ResponseNam espace="http://example/NsProblem/A")]
public NsProblem.A.Som ething[] GetArrayA() { return null; }

[WebMethod]
[SoapDocumentMet hod(ResponseNam espace="http://example/NsProblem/B")]
public NsProblem.B.Som ething[] GetArrayB() { return null; }
}
}