The client that is calling my implemented service is using gsoap. So the client calls our webservice and we give back a response. When returning the response using our implemented service using CXF all fails but replying the same response using soap-ui it works ..
2012/5/4 Daniel Kulp <[email protected]>: > > Do you know anything about the other server? The *COMMON* cause of this is > that it's an old version of .NET that doesn't support HTTP 1.1 chunking. > > See: > http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport%28includingSSLsupport%29-ANoteAboutChunking > > and the docs on that page to turn it off and seeing if that helps. > > Dan > > > > On Friday, May 04, 2012 03:46:20 PM Marco Pas wrote: >> Hi there, >> >> i have a problem in which i seem to get stuck.. >> >> The case is that i have implemented a webservice which is called by an >> external system. This system calls a webservice and gets a immediate >> response. >> A strange thing occurs when i run the cxf service and gave back a >> payload, then the external systems is not able to handle my request. >> When i return the "same" (copy and paste from the logfile payload) >> using SOAP-UI the external system is perfectly capable of handling the >> response. >> >> So.. to be short.. i have generated a service according to a wsdl >> file, implemented the service and the external system is calling my >> service, i return an object .. >> >> When returning from cxf it fails --> cxf complains: >> org.apache.cxf.interceptor.Fault: Could not send Message... >> Caused by: org.apache.cxf.transport.http.HTTPException: HTTP response >> '400: Bad Request' when communicating with ... >> >> When returning from SOAP-UI --> all faces are happy and it works.. >> >> Any suggestions on how to tackle this issue?? >> >> /Marco > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com >
