*Hi **Lawrence*,
I want to know to force Axis2 to user HTTP/1.0?
thanks
2009/11/18 Lawrence Yao <mla...@gmail.com>
> Thanks Andreas for pointing out the problem. Axis2 is using HTTP/1.1
> while the mono server is only HTTP/1.0 capable, therefore the chunked
> transfer caused the error message.
>
> I have solved the problem by forcing Axis2 to use HTTP/1.0.
>
> Cheers,
> Lawrence.
>
>
> On Tue, Nov 17, 2009 at 11:37 PM, Andreas Veithen
> <andreas.veit...@gmail.com> wrote:
> > Please see:
> >
> > http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1
> >
> > On Tue, Nov 17, 2009 at 04:12, Lawrence Yao <mla...@gmail.com> wrote:
> >> Hello all,
> >>
> >> I have written a client using Axis2 (version 1.5) that attempts to
> >> access a Web service written in C#/mono. Whenever I attempt to
> >> connect, I receive the following exception:
> >>
> >> org.apache.axis2.AxisFault: Could not deserialize Soap message
> >>
> >> I noticed that the SOAP message sent to the server is incorrectly
> >> formatted and contains additional characters. I captured the entire
> >> message shown below:
> >>
> >>
> >> POST /XXXXImport.asmx HTTP/1.1
> >> Content-Type: text/xml; charset=UTF-8
> >> SOAPAction: "http://127.0.0.1:8080/XXXXImport.asmx/xxxxImport";
> >> User-Agent: Axis2
> >> Host: localhost:8080
> >> Transfer-Encoding: chunked
> >>
> >> 193
> >> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
> >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> "><soapenv:Body><ns1:rdthImport
> >> xmlns:ns1="http://127.0.0.1:8080/XXXXImport.asmx
> "><ns1:codesIn>Code</ns1:codesIn><ns1:startdateIn>01/01/2003</ns1:startdateIn><ns1:enddateIn>15/01/2003</ns1:enddateIn><ns1:resultid>46525511.csv</ns1:resultid></ns1:rdthImport></soapenv:Body></soapenv:Envelope>
> >> 0
> >>
> >>
> >> In my opinion, the characters "193" and "0" should not appear where
> >> they are (before and after the XML message, respectively). Once, I
> >> also got "1b3" to appear in place of "193" when the contents of the
> >> XML message was different. I believe these additional characters are
> >> causing the "Could not deserialize Soap message" exception above,
> >> because I have written a PHP client to connect to the same Web service
> >> and it worked. When comparing the two SOAP messages, the PHP client's
> >> message did not have these additional characters.
> >>
> >> I have tested that this happens when using Axis2 versions 1.4.1, 1.5
> >> and 1.5.1. Oddly enough, I did not encounter problems when using Axis2
> >> clients to connect to Axis2 Web services. Any ideas?
> >>
> >> Thanks,
> >> Lawrence.
> >>
> >
>
