axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (AXIS-1299) document/literal service generates invalid WSDL documentOrder attribute
Date Mon, 12 Apr 2004 14:51:44 GMT
The following comment has been added to this issue:

     Author: Tom Jordahl
    Created: Mon, 12 Apr 2004 7:50 AM
       Body:
If parameterOrder="" we should leave this off the generated WSDL, but it looks like there
is a bug in the wrapped processing that misses the single part.  We might want to fix both
problems.


---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1299?page=comments#action_32887

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1299
    Summary: document/literal service generates invalid WSDL documentOrder attribute
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Nelson Minar

    Created: Sun, 11 Apr 2004 5:37 PM
    Updated: Mon, 12 Apr 2004 7:50 AM

Description:
The following WSDD:

 <service name="Demo" provider="java:RPC" style="wrapped" use="literal">
  <parameter name="allowedMethods" value="*"/>
  <parameter name="className" value="com.google.soap.base.DemoService"/>
  <beanMapping qname="ns:DemoData" xmlns:ns="http://demo.google.com" languageSpecificType="java:com.google.soap.base.DemoService$DemoData"
/>
 </service>

For a java method like this:
  public String echoString(String s) {
    return s;
  }

Generates WSDL with bits like this:
      <wsdl:operation name="echoString" parameterOrder="">
         <wsdl:input name="echoStringRequest" message="impl:echoStringRequest" />
         <wsdl:output name="echoStringResponse" message="impl:echoStringResponse" />
      </wsdl:operation>

Which SOAPScope's Analyze module complains about. In particular, it says that having parameterOrder=""
doesn't match the WSDL Schema: the parameterOrder attribute must have at least one character
in it. If I declare the service to be rpc/encoded in the WSDD then it generates things like
parameterOrder="s" which seems plausible.

parameterOrder is an optional attribute of WSDL. Is it safe to leave it off? I believe WS-I
BP1.0a says that parameter order always matters and for a document/literal service it can
just use the schema definition, right?



---------------------------------------------------------------------
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