The addition of doWorkResponse is probably dictated by the JAX-WS
specification that CXF has to implement. Also, removal of the
doWorkResponse would probably harm interoperability (and portability of)
SOAP clients, because they rely on the WSDL to generate needed artifacts.
WSDL 2.0 doesn't use wsdl:messages at all, so your concern may go away with
the new standard (assuming WSDL 2.0 will ever become the standard.)
Glen
Hannes Holtzhausen wrote:
>
> Hi
>
> I have a service interface that looks like follows:
>
> public interface MyService
> {
> public void doWork(MyWork work);
> }
>
> By default the doWork interface operation would have 2 messages
> associated with it
> in the generated WSDL when using the simple frontend e.g:
>
> <wsdl:message name="doWork">
> <wsdl:part element="tns:doWork" name="parameters">
> </wsdl:part>
> </wsdl:message>
> <wsdl:message name="doWorkResponse">
> <wsdl:part element="tns:doWorkResponse" name="parameters">
> </wsdl:part>
> </wsdl:message>
>
> Are there any configuration options available that will
> force the simple frontend to exclude the <method name>Response
> messages from the generated WSDL for all interface operations with
> a void return type?
>
> Thanks
> Hannes
>
--
View this message in context:
http://cxf.547215.n5.nabble.com/Oneway-service-operations-using-simple-frontend-tp1960887p2228242.html
Sent from the cxf-user mailing list archive at Nabble.com.
