axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Sosnoski (JIRA)" <>
Subject [jira] Commented: (AXIS-313) Axis does not understand default namespace; will not interoperate with.NET
Date Mon, 28 Feb 2005 23:21:51 GMT
     [ ]
Dennis Sosnoski commented on AXIS-313:

This should be reopened. Default namespaces do apply to QNames character data content. The
most widely used example I've seen of this is in schema definitions, where using the schema
namespace as the default lets you reference standard schema types without needing to use a
prefix (as in <element name="text" type="string"/>).

> Axis does not understand default namespace; will not interoperate with.NET
> --------------------------------------------------------------------------
>          Key: AXIS-313
>          URL:
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: current (nightly)
>  Environment: Operating System: All
> Platform: All
>     Reporter: hhuang
>     Assignee: Axis Developers Mailing List

> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message