axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Closed: (AXIS-1300) Axis 1.2beta puts namespace on soapbody for document/literal services; violates BP1.0a
Date Mon, 12 Apr 2004 21:06:43 GMT

   The following issue has been closed.

   Resolver: Davanum Srinivas
       Date: Mon, 12 Apr 2004 2:06 PM

View the issue:

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

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Axis
             WSDL processing
   Fix Fors:
             current (nightly)
             1.2 Beta

   Reporter: Nelson Minar

    Created: Sun, 11 Apr 2004 6:30 PM
    Updated: Mon, 12 Apr 2004 2:06 PM

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">
  <parameter name="allowedMethods" value="*"/>
  <parameter name="className" value="demo.DemoService"/>
  <beanMapping qname="ns:DemoData" xmlns:ns="urn:demoNamespace" languageSpecificType="java:demo.DemoService$DemoData"

Results in the following bit inside my WSDL:

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

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.

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