I would also check Wireshark[1]--it may give you a little bit more feedback about what's going on.
HTH, Glen [1] http://www.jroller.com/gmazza/entry/wireshark_usage_for_cxf Am Mittwoch, den 16.04.2008, 07:00 -0400 schrieb Benson Margulies: > Personally, I can't imagine a way to persuade CXF to send 'ed' and '0'. Can > you send us your cxf.xml or java code that you use? > > On Wed, Apr 16, 2008 at 3:37 AM, Jan Pechanec <[EMAIL PROTECTED]> wrote: > > > > > I have problem with SOAP request message generated with Apache CXF 2.0.4. > > I generated java client from WSDL (wsdl2java), and tried to call web > > service running in the cobol MicroFocus Enteprise Server - the response was > > following: > > ... > > <faultcode>Client</faultcode> > > <faultstring>Error in client request message</faultstring> > > ... > > > > I suppose it means that SOAP request message is bad for the server side of > > web service. > > I tried following: > > Apache CFX client -> cobol server : Error in client request message > > soapUI client generated from WSDL -> cobol server : OK > > Apache CFX client -> soapUI Mock service generated from WSDL : OK > > > > In the tcpmon I can see that there are strange chars ("ed", "0") around > > SOAP message. > > I suppose this is the problem, but why there are these chars? > > See below. > > > > ------------------------------------ > > POST / HTTP/1.1 > > Content-Type: text/xml; charset=UTF-8 > > SOAPAction: "" > > Accept: * > > Cache-Control: no-cache > > Pragma: no-cache > > User-Agent: Java/1.6.0_04 > > Host: localhost:8081 > > Connection: keep-alive > > Transfer-Encoding: chunked > > > > ed > > <soap:Envelope > > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><Read > > xmlns="http://tempuri.org/wmapserv > > "><BookStockno>1111</BookStockno><BookTitle></BookTitle><BookAuthor></BookAuthor></Read></soap:Body></soap:Envelope> > > 0 > > ---------------------------------- > > > > Thank you for any help, any hint, > > Jan > > > >
