[ 
http://issues.apache.org/jira/browse/AXIS2-1185?page=comments#action_12436277 ] 
            
Brennan Spies commented on AXIS2-1185:
--------------------------------------

I am going to correct myself here. Use of the 'type' attribute on 
definitions/message/part is not allowed for document/literal binding by WS-I 
(Basic Profile, Section 4.4.1). Only for RPC syle. For the sake of being 
circumspect, the Axis 2 code generator should print a warning about this or 
throw an exception.

> Generation of a return message when 'type' is specified on the output message 
> part
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-1185
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1185
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.0
>         Environment: Axis 2.0 build: 2006-09-18, Windows XP
>            Reporter: Brennan Spies
>
> When specifying a 'type' rather than 'element' on a WSDL message part, the 
> Axis 2.0 code generation does not put a return type in the corresponding Java 
> method, hence the returned SOAP message would not be meaningful. 
> For example,
> <message name="Response">
>      <part name="output" type="ns:responseType"/>
> </message>
> If the operation is
> <wsdl:portType name="ActionInterface">
>       <wsdl:operation name="Action">
>               <wsdl:input message="tns:Request" />
>               <wsdl:output message="tns:Response" />
>       </wsdl:operation>
> </wsdl:portType>
> The Axis code generator (with XMLBeans databinding) will generate an "Action" 
> method in the skeleton that has a "void" return type.

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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to