CXF Client: Outbound SOAP request - Missing <soap:Body>
-------------------------------------------------------

                 Key: CXF-2405
                 URL: https://issues.apache.org/jira/browse/CXF-2405
             Project: CXF
          Issue Type: Bug
    Affects Versions: 2.2.3, 2.2.2
         Environment: Tomcat 6.0.18, CXF2.2.3
            Reporter: Vikas Narang


Hi,

I am facing an issue where the outbound SOAP request from the CXF client seems 
to be missing the SOAP body.
I enabled logging and below is how the log looks that show the Outbound/Inbound 
SOAP request/response.

The deployed web service has 2 webmethods "getFirstName()" and "getLastName()" 
and calls to both of these returns the result from the getFirstName() method, 
see below log:


***********************************************************************************************************
Aug 27, 2009 7:23:15 PM org.apache.cxf.bus.spring.BusApplicationContext 
getConfigResources
INFO: No cxf.xml configuration file detected, relying on defaults.
Aug 27, 2009 7:23:17 PM 
org.apache.cxf.service.factory.ReflectionServiceFactoryBean buildServiceFromWSDL
INFO: Creating Service {http://net.ibs.WSGetName}WSGetNameService from WSDL: 
file:/C:/WSGetName.wsdl
Invoking getLastName...
Aug 27, 2009 7:23:17 PM 
org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose
INFO: Outbound Message
---------------------------
ID: 1
Address: http://localhost:16899/axis/services/WSGetName
Encoding: UTF-8
Content-Type: text/xml
Headers: {SOAPAction=[""], Accept=[*/*]}
Payload: <soap:Envelope 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body 
/></soap:Envelope>
--------------------------------------
Aug 27, 2009 7:23:17 PM org.apache.cxf.interceptor.LoggingInInterceptor logging
INFO: Inbound Message
----------------------------
ID: 1
Encoding: UTF-8
Content-Type: text/xml;charset=utf-8
Headers: {content-type=[text/xml;charset=utf-8], Date=[Thu, 27 Aug 2009 
13:53:17 GMT], transfer-encoding=[chunked], Server=[Apache-Coyote/1.1]}
Payload: <?xml version="1.0" encoding="UTF-8"?><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";><soapenv:Body><getFirstNameReturn
 
xmlns="http://net.ibs.WSGetName";>Vikas</getFirstNameReturn></soapenv:Body></soapenv:Envelope>
--------------------------------------
getLastName.result=Vikas
Invoking getFirstName...
Aug 27, 2009 7:23:17 PM 
org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose
INFO: Outbound Message
---------------------------
ID: 2
Address: http://localhost:16899/axis/services/WSGetName
Encoding: UTF-8
Content-Type: text/xml
Headers: {SOAPAction=[""], Accept=[*/*]}
Payload: <soap:Envelope 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body 
/></soap:Envelope>
--------------------------------------
Aug 27, 2009 7:23:17 PM org.apache.cxf.interceptor.LoggingInInterceptor logging
INFO: Inbound Message
----------------------------
ID: 2
Encoding: UTF-8
Content-Type: text/xml;charset=utf-8
Headers: {content-type=[text/xml;charset=utf-8], Date=[Thu, 27 Aug 2009 
13:53:17 GMT], transfer-encoding=[chunked], Server=[Apache-Coyote/1.1]}
Payload: <?xml version="1.0" encoding="UTF-8"?><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";><soapenv:Body><getFirstNameReturn
 
xmlns="http://net.ibs.WSGetName";>Vikas</getFirstNameReturn></soapenv:Body></soapenv:Envelope>
--------------------------------------
getFirstName.result=Vikas

************************************************************************************************************

The request is missing the soap:Body information:
Payload: <soap:Envelope 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body 
/></soap:Envelope>

I am attaching the WDSL , CXF client and also the deployed web service class 
for reference.

Any help on this is greatly appreciated.

Thanks!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to