0 Replies Latest reply on Jan 20, 2016 3:38 AM by Nicklas Karlsson

    CXF operation name in request

    Nicklas Karlsson Master

      Hi,

       

        I'm trying to duplicate a service (wsconsume-generated) for testing purposes from a RPC style WSDL document but for some reason there is a difference in e.g. what requests SoapUI generate against my service and the real one. The difference is that the real requests wrap the call in the operation name, e.g.

       

      <?xml version="1.0" encoding="UTF-8"?>
      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="urn">
        <soap:Body>
           <ns:getStuff>
              <param>stuff</param>
           </ns:getStuff>
        </soap:Body>
      </soap:Envelope>
      
      
      

       

      and my own service eats

       

      <?xml version="1.0" encoding="UTF-8"?>
      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="urn">
        <soap:Body>
           <param>stuff</param>
        </soap:Body>
      </soap:Envelope>
      
      
      

       

      I've tried different @SOAPBinding(style = SOAPBinding.Style.RPC, parameterStyle=ParameterStyle.WRAPPED/BARE) settings but no go. Any tips on getting the wrapped operation name accepted by the service? Now it complains that the operation name element was unexpected.

       

      The generated method annotations are

       

         @WebMethod
         @WebResult(name = "return", targetNamespace = "urn", partName = "return")
         public String getStuff(
            @WebParam(partName = "String_1", name = "String_1") final String stuff)
      

       

      but fiddling with the name etc doesn't produce the wrapped operation name in the SoapUI sample request.

       

      Thanks in advance,

      Nik