cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "maomaode (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-650) rule non wrapper style in jaxws not respected in cxf tools
Date Tue, 15 May 2007 04:03:16 GMT

    [ https://issues.apache.org/jira/browse/CXF-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495853
] 

maomaode commented on CXF-650:
------------------------------

We already have a testcase to cover this inout header, it's testutils/src/main/resources/wsdl/soap_header.wsdl

<message name="inoutHeaderRequest">
<part element="tns:inoutHeader" name="me"/>
<part element="tns:SOAPHeaderInfo" name="header_info"/>
</message>
<message name="inoutHeaderResponse">
<part element="tns:inoutHeaderResponse" name="the_response"/>
<part element="tns:SOAPHeaderInfo" name="header_info"/>
</message>

The only difference is that name attribute of the request and response message is different

But even

<message name="inoutHeaderRequest">
<part element="tns:inoutHeader" name="me"/>
<part element="tns:SOAPHeaderInfo" name="header_info"/>
</message>
<message name="inoutHeaderResponse">
<part element="tns:inoutHeaderResponse" name="me"/>
<part element="tns:SOAPHeaderInfo" name="header_info"/>
</message>

will generate the same signature of the method, i.e:

public org.apache.samples.headers.InoutHeaderResponse inoutHeader(
@WebParam(targetNamespace = "http://apache.org/samples/headers", partName = "me", name = "inoutHeader")
org.apache.samples.headers.InoutHeader me,
@WebParam(targetNamespace = "http://apache.org/samples/headers", header = true, mode = Mode.INOUT,
partName = "header_info", name = "SOAPHeaderInfo")
javax.xml.ws.Holder<org.apache.samples.headers.SOAPHeaderData> headerInfo
); 

I tested with JAXWS RI , i got the same results.

And after read the JAXWS Spec, section 3.6.6.2, we know that return type can not be void.
If it does, then break the third rule, i.e

"If it has a return type of void it MUST have at most one in/out or out non-header parameter"

>From the description of the issue, i can see that you said it should be void, but you
didn't give the reason.

> rule non wrapper style in jaxws not respected in cxf tools
> ----------------------------------------------------------
>
>                 Key: CXF-650
>                 URL: https://issues.apache.org/jira/browse/CXF-650
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>            Reporter: Julien le Colloec
>
> the code generated with cxf tool for the mtosi wsdl file ConfigurationService.wsdl is
wrong. 
> The return type of the operation getTransmissionDescriptor should be void and we should
have an additional argument 
> representing an out. 
> The part of the wsdl ,which is not correctly handled, is at the bottom of this page .

>     public v1.tmf854.GetTransmissionDescriptorResponseT getTransmissionDescriptor( 
>         @WebParam(targetNamespace = "tmf854.v1", header = true, mode = Mode.INOUT, partName
= "mtosiHeader", name = "header") 
>         javax.xml.ws.Holder<v1.tmf854.HeaderT> mtosiHeader, 
>         @WebParam(targetNamespace = "tmf854.v1", partName = "mtosiBody", name = "getTransmissionDescriptor")

>         v1.tmf854.GetTransmissionDescriptorT mtosiBody 
>     ) throws ProcessingFailureException; 
> <wsdl:message name="getTransmissionDescriptor"> 
>     <wsdl:documentation> 
>     The getTransmissionDescriptor request message. 
>     </wsdl:documentation> 
>     <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/> 
>     <wsdl:part name="mtosiBody" element="tmf854XSD:getTransmissionDescriptor"/>

>   </wsdl:message> 
>   <wsdl:message name="getTransmissionDescriptorResponse"> 
>     <wsdl:documentation> 
>     The getTransmissionDescriptor response message. 
>     </wsdl:documentation> 
>     <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/> 
>     <wsdl:part name="mtosiBody" element="tmf854XSD:getTransmissionDescriptorResponse"/>

>   </wsdl:message> 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message