axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Created: (AXIS-1300) Axis 1.2beta puts namespace on soapbody for document/literal services; violates BP1.0a
Date Mon, 12 Apr 2004 01:31:49 GMT
Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1300

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1300
    Summary: Axis 1.2beta puts namespace on soapbody for document/literal services; violates
BP1.0a
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Nelson Minar

    Created: Sun, 11 Apr 2004 6:30 PM
    Updated: Sun, 11 Apr 2004 6:30 PM

Description:
I believe this is a bug in Axis that will hamper passing BP1.0a

The following bit of WSDD:

<service name="Demo" provider="java:RPC" style="wrapped" use="literal">
  <namespace>urn:demoNamespace</namespace>
  <parameter name="allowedMethods" value="*"/>
  <parameter name="className" value="demo.DemoService"/>
  <beanMapping qname="ns:DemoData" xmlns:ns="urn:demoNamespace" languageSpecificType="java:demo.DemoService$DemoData"
/>
</service>

Results in the following bit inside my WSDL:

<wsdl:binding name="DemoSoapBinding" type="impl:DemoService">
  <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="echoString">
      <wsdlsoap:operation soapAction="" />
      <wsdl:input name="echoStringRequest">
        <wsdlsoap:body use="literal" namespace="urn:demoNamespace" />
      </wsdl:input>

BP1.0a R2716 says that the wsdlsoap:body element should have no namespace attribute because
the embedded schema for the doc/literal service will define it. The namespace Axis is putting
in is OK (it matches the schema), but it's invalid according to SOAPScope's interpretation
of BP1.0a.

I think the fix is simply to not emit the namespace attribute, but I'd sure want to run it
through a document/literal interop suite before trying that.

http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html#R2716


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message