[jira] Updated: (CXF-161) wsdl2java doesn't map parameter order correctly

["Peter Jones (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/CXF-161?page=all ]

Peter Jones updated CXF-161:
----------------------------

    Attachment: header2.wsdl

> wsdl2java doesn't map parameter order correctly
> -----------------------------------------------
>
>                 Key: CXF-161
>                 URL: http://issues.apache.org/jira/browse/CXF-161
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>            Reporter: Peter Jones
>         Attachments: header2.wsdl
>
>
> According to the "Parameter Order" section of jaxws spec, unlisted parameters mapped from in and in/out parts appear in the same order the corresponding parts appear in the input message.
> I'll attach a test wsdl in which wsdl2java doesn't follow this rule.  Basically, the wsdl input message is:
>     ...
>     <message name="headerRequest">
>         <part element="tns:HeaderInfo" name="header_info"/>
>         <part element="tns:Header" name="the_request"/>
>     </message>
> (header_info first, the_request second) - but the generated method signature 
> has theRequest parameter first and headerInfo second:
>     ...
>     public org.apache.header2.HeaderResponse headerMethod(
>         @WebParam(targetNamespace = "http://apache.org/header2", partName = "the_request", name = "Header")
>         org.apache.header2.Header theRequest,
>         @WebParam(targetNamespace = "http://apache.org/header2", header = true, mode = Mode.INOUT, partName = "header_info", name = "HeaderInfo")
>         javax.xml.ws.Holder<org.apache.header2.HeaderData> headerInfo
>     );
>     

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira