DO NOT REPLY [Bug 12451] New: - Axis does not understand default namespace; will not interoperate with.NET

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12451>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12451

Axis does not understand default namespace; will not interoperate with.NET

           Summary: Axis does not understand default namespace; will not
                    interoperate with.NET
           Product: Axis
           Version: current (nightly)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: hhuang@kodak.com


Bug in RC1

If NS:TypeB is a complexType extending from NS:TypeA, and elementA is of 
NS:TypeA, the following should be accepted by Axis:

<methodCall xmlns="NS">
  <elementA xsi:type="TypeB">
</methodCall>

However, Axis insists on an explicit namespace:

<methodCall xmlns="NS" xmlns:explicit="NS">
  <elementA xsi:type="explicit:TypeB">
</methodCall>

Axis is too strict. It should accept default namespaces. .NET uses xmlns="foo" 
style namespaces for doc/literal messages. This bug makes Axis and .NET non-
interoperable for inherited classes/types.

-Han Huang
hhuang@kodak.com