axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Assigned: (AXIS-1129) complexType in SOAP response has namespace prefix, chokes .net clients
Date Mon, 22 Mar 2004 14:28:58 GMT

   The following issue has been re-assigned.

   Assignee: Glen Daniels (
   Assigner: Davanum Srinivas (
       Date: Mon, 22 Mar 2004 6:27 AM
Assigning to Glen.
View the issue:

Here is an overview of the issue:
        Key: AXIS-1129
    Summary: complexType in SOAP response has namespace prefix, chokes .net clients
       Type: Bug

     Status: Reopened

    Project: Axis

   Assignee: Glen Daniels
   Reporter: Matt Bateman

    Created: Thu, 20 Nov 2003 2:57 AM
    Updated: Mon, 22 Mar 2004 6:27 AM
Environment: Operating System: All
Platform: All

The SOAP response from Axis for an RPC style service that returns complexTypes 
in the response places a namespace prefix on the complexType elements.  .NET 
clients cannot hanlde this prefix.

There was a thread about this on the user list a while back.  Apparently in 
April of 2002, this issue was fixed.  The thread is here:  But in both 
the 1.0 and 1.1 releases, this issue remains.  At the request of Davanum, I've 
tested against the latest in CVS.  The issue remains there as well.

I know that this has been discussed before but I was unable to find any other 
references in Bugzilla or the axis-user archive (searching 
for ".net", "prefix", "namespace", "complexType", "interop", etc.).

The respone that axis (compiled from the latest cvs) returns:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="" 
   <ns1:op2Return xsi:type="ns1:MyCustomType">
    <ns1:lotsOfBob xsi:type="ns1:BobType">
     <ns1:AString xsi:type="xsd:anySimpleType">bobEl1</ns1:AString>
    <ns1:lotsOfBob xsi:type="ns1:BobType">
     <ns1:AString xsi:type="xsd:anySimpleType">bobEl2</ns1:AString>
    <ns1:bob xsi:type="ns1:BobType">
     <ns1:AString xsi:type="xsd:anySimpleType">bob value</ns1:AString>
    <ns1:bar xsi:type="xsd:anySimpleType">fooEl1</ns1:bar>
    <ns1:bar xsi:type="xsd:anySimpleType">fooEl2</ns1:bar>
    <ns1:bar xsi:type="xsd:anySimpleType">fooEl3</ns1:bar>
    <ns1:foo xsi:type="xsd:anySimpleType">foo value</ns1:foo>

(As a side note, I'm not sure about the "anySimpleType", with axis 1.1 the type 
values are the correct xsd types - xsd:string).

Notice the ns1 prefix on every element.  A .net client accepts the response, 
(not throwing any errors) but all values are null.  Taking out the 
prefixes, .net correctly understands the response.  I don't know whether 
prefixes or no prefixes in the SOAP message is correct or if both are.  At this 
point though, we are unable to invoke any rpc service that returns a complex 
type hosted by axis with a .net client.

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