Re: Invalid SOAP message

2008-04-17 Thread Jan Pechanec
Yes! That's the problem! I made it via code and it works. Thank you very much, Jan Daniel Kulp [EMAIL PROTECTED] napsal dne 16.04.2008 19:11:15: Those extra character are due to the Transfer-Encoding: chunked. It looks like the cobol server doesn't support the chunked encoding.You

Invalid SOAP message

2008-04-16 Thread Jan Pechanec
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: ... faultcodeClient/faultcode faultstringError in client request

Re: Invalid SOAP message

2008-04-16 Thread 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

Re: Invalid SOAP message

2008-04-16 Thread Jan Pechanec
Just a small note about test case - I run it over plain Apache CXF installation, no changes. Jan Benson Margulies [EMAIL PROTECTED] napsal dne 16.04.2008 13:00:10: 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?

Re: Invalid SOAP message

2008-04-16 Thread Daniel Kulp
Those extra character are due to the Transfer-Encoding: chunked. It looks like the cobol server doesn't support the chunked encoding.You can look at the docs for the HTTPConduit at: http://cwiki.apache.org/CXF20DOC/client-http-transport.html to turn off the chunking. Via code, it would