Hi Chris, Thanks for your reply! I am pretty new to the whole Http Header stuff and maybe you could point me into the right direction. Should I use something like wireshark to examine the http headers?
And can I control the http headers from cxf? I was under the impression that just responding to a soap call would be enough. Op May 4, 2012 om 16:14 heeft Christopher Riley <[email protected]> het volgende geschreven: > Hi Marco, > > It may not be the SOAP message that is the problem but rather the HTTP > Headers/Details that is different. It wasn't clear in the log if you > captured the entire HTTP payload including the SOAP Envelope in the log. I > would start there and see what mismatch may be occurring. > > Chris > > On Fri, May 4, 2012 at 9:46 AM, Marco Pas <[email protected]> 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 >> > > > > -- > Chris Riley, Partner > HKM Consulting LLC > (w) hkmconsultingllc.com > (o) 774.553.5314 > (m) 508.273.3102 > (f) 774.553.5316
