Re: Adding SAAJInInterceptor breaks the RPCInInterceptor

[neela]

Hi Daniel,
Thanks for looking into this.
I checked my service & response again.
I see 2 response in the SOAP BODY. as below. One is empty result with
namespace and other proper result with out namespace.


<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 <SOAP-ENV:Header
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/>
  <soapenv:Body>
   <simpleIntResponse xmlns="http://www.aspect.com/rpcLiteralSimple/";>
   <simpleIntResponse xmlns="">4</simpleIntResponse></simpleIntResponse>
  </soapenv:Body>
</soapenv:Envelope>


My Test code is as below.

        Object[] inParams = new Object[1];
        String wsdlURL = "http://nshankara-o7010:8080/?WSDL";;
        String methodName = "simpleString";
        inParams[0] = "sometext";

        DynamicClientFactory dcf = DynamicClientFactory.newInstance();
        Client client = dcf.createClient( wsdlURL );
        final Endpoint port = client.getEndpoint();
        BindingInfo bindingInfo = port.getBinding().getBindingInfo();
        Collection<BindingOperationInfo> operations =
bindingInfo.getOperations();
        BindingOperationInfo bindingOpInfo = getOperation( operations,
methodName);

        try
        {
            client.getInInterceptors().add( new SAAJInInterceptor() );
            client.getInInterceptors().add( new VOSoapResponseInterceptor()
);
            Object[] res = client.invoke( bindingOpInfo, inParams );
            if ( res != null && res.length > 0 )
            {
                System.out.println( res[0] );
            }
        }
        catch ( Exception e )
        {
            e.printStackTrace();
        }


Am I doing something wrong?

Regards,
Neela




--
View this message in context: 
http://cxf.547215.n5.nabble.com/Adding-SAAJInInterceptor-breaks-the-RPCInInterceptor-tp5744593p5744609.html
Sent from the cxf-user mailing list archive at Nabble.com.