The issue is here: https://issues.apache.org/jira/browse/AXIS2-1185
-----Original Message----- From: Spies, Brennan Sent: Monday, September 18, 2006 11:49 AM To: [email protected]; [EMAIL PROTECTED] Subject: RE: [Axis2] Using 'type' attribute for the message part Yes, I am using the most recent nightly build. The input and output is Doc/literal... <wsdl:binding name="ActionSoapHttp" type="tns:ActionInterface"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"; /> <wsdl:operation name="Action"> <soap:operation soapAction="urn:ejgallo:workflow:service:action/Action" /> <wsdl:input> <soap:body use="literal" /> </wsdl:input> <wsdl:output> <soap:body use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> I can file a bug (no problem) since it's clear the lack of a return doc is a bug, but I also wanted to know what is meant when a 'type' is specified in the WSDL, i.e., what SHOULD be the result of such a configuration in terms of what is generated in the SOAP, and more specifically to Axis2, the generated classes? Brennan -----Original Message----- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Monday, September 18, 2006 11:42 AM To: [email protected]; [EMAIL PROTECTED] Subject: Re: [Axis2] Using 'type' attribute for the message part Hi, What kind of binding do you have ? Ajith On 9/18/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Are u using the nightly build? If so, please open a issue/bug. > > thanks, > dims > > On 9/18/06, Spies, Brennan <[EMAIL PROTECTED]> wrote: > > Axis devs, > > > > Got a question regarding the use of types for message parts rather than > > elements...specifically, what are the semantics of it? Reading the WSDL spec > > does not clarify this for me. > > > > For example, suppose you have an output message defined as > > > > <message name="Response"> > > <part name="output" type="ns:responseType"/> > > </message> > > > > Using the Axis code generator with XMLBeans databinding, the ResponseType > > class will be generated, but there is no corresponding *Document class. Also, > > the methods in the generated code look more like an IN ONLY MEP rather than > > IN-OUT--i.e., the skeleton has no return value, hence no meaningful SOAP > > response is generated. > > > > Brennan > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
