Hi, I've used CXF on a few projects and I'm seriously impressed with the quality of the product. I'm currently porting some old Axis1 webservices over to CXF and while my new WS works perfectly, I do have a little problem with the WSDL generated. The problem is that I need a fairly old product to parse the WSDL and it's currently failing. I don't think this is the fault of CXF but perhaps CXF can be configured to produce a WSDL that this old product seems to accept.
I've annotated my interface with the following: @WebService @SOAPBinding(style=Style.RPC, use=Use.LITERAL) and it's producing WSDL for a method as follows: <wsdl:operation name="authenticate"> <soap:operation soapAction="" style="rpc"/> <wsdl:input name="authenticate"> <soap:body namespace="http://services.integration.javasystemsolutions.com/"; use="literal"/> </wsdl:input> <wsdl:output name="authenticateResponse"> <soap:body namespace="http://services.integration.javasystemsolutions.com/"; use="literal"/> </wsdl:output> </wsdl:operation> However Axis1.4 generates the following WSDL: <wsdl:operation name="authenticate"> <wsdlsoap:operation soapAction=""/> <wsdl:input name="authenticateRequest"> <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; namespace="http://ws.webapp.javasystemsolutions.com"; use="encoded"/> </wsdl:input> <wsdl:output name="authenticateResponse"> <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; namespace="http://localhost:8080/myservice"; use="encoded"/> </wsdl:output> </wsdl:operation> Why do they look subtly different and is it possible for CXF to be configured to produce something like Axis, purely for the benefit of a product that is a bit difficult.. :) Thanks for the wonderful product. John
