axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Closed: (AXIS-1299) document/literal service generates invalid WSDL documentOrder attribute
Date Mon, 12 Apr 2004 20:49:43 GMT

   The following issue has been closed.

   Resolver: Davanum Srinivas
       Date: Mon, 12 Apr 2004 1:48 PM

View the issue:

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

     Status: Closed
   Priority: Major
 Resolution: FIXED

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

   Reporter: Nelson Minar

    Created: Sun, 11 Apr 2004 5:37 PM
    Updated: Mon, 12 Apr 2004 1:48 PM

The following WSDD:

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

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

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?

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