This is a standard example of HTTP Chunking which is part of the HTTP 1.1 spec. The server should understand it. So really this is a bug in your server :)
If you look at: Transfer-Encoding: chunked 387 that basically says there is a chunk of 387 bytes coming. The 0 indicates the size of the next chunk (0) meaning the message is finished. You can fix this by turning chunking off - the code is different if you are on Axis1 or Axis2. Paul On Wed, Apr 9, 2008 at 11:01 AM, Yasir Arsalan <[EMAIL PROTECTED]> wrote: > > > I am having a problem in making a call using Axis client. I have generated > the client in java using wsdl file. when I make the call using this client > it generates a SOAP request message, that I have pasted below, which > contains a terminating zero in it . This terminating zero is creating > problem for the web service server to recognize the recieving request > message as a valid xml format for SOAP. Does any body have idea why this > terminating zero is for? How can I remove this terminating zero from the > SOAP request. SOAP request & response messages are as follows: > > > *********************************SOAP > Request************************************************* > > POST http://ws-server:1080/eproxy/service/security HTTP/1.1 > Content-Type: text/xml; charset=utf-8 > SOAPAction: "http://ABC.com/Security/LoginExtended"; > User-Agent: Axis/1.4 > Host: vs-devbwb:1080 > Proxy-Connection: Keep-Alive > Transfer-Encoding: chunked > 387 > <?xml version="1.0" encoding="UTF-8"?> > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > <soapenv:Header> > <ns1:BrokerHeader soapenv:mustUnderstand="0" > xmlns:ns1="http://ABC.com/Common";> > <SystemCredentialStore>CorporateAD</SystemCredentialStore> > <SystemId>APPACCTEST</SystemId> > <SystemPassword>ABC</SystemPassword> > <SystemCredentialStore>CorporateAD</SystemCredentialStore> > <UserId>APPACCTEST</UserId> > <UserPassword>ABC</UserPassword> > <ITData> > <Entries> > <Entry> > <key>SystemIPAddress</key> > <value>10.0.223.120</value> > </Entry> > <Entry> > <key>UserIPAddress</key> > <value>10.0.31.52</value> > </Entry> > </Entries> > </ITData> > </ns1:BrokerHeader> > </soapenv:Header> > <soapenv:Body> > <LoginExtended xmlns="http://ABC.com/Security";> > <stateInfo>state</stateInfo> > </LoginExtended> > </soapenv:Body> > </soapenv:Envelope>0 > > > > ******************************************SOAP > Response************************************** > HTTP/1.1 500 Internal Server Error > Connection: close > Date: Mon, 07 Apr 2008 16:56:51 GMT > Server: Microsoft-IIS/6.0 > X-Powered-By: ASP.NET > X-AspNet-Version: 1.1.4322 > Content-Length: 376 > Cache-Control: private > Content-Type: text/xml; charset=UTF-8 > > <?xml version="1.0" encoding="utf-8"?> > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > <soapenv:Body> > <soapenv:Fault> > <faultcode > xmlns:tns="http://schemas.xmlsoap.org/soap/envelope/";>tns:Client.InvalidMessage</faultcode> > <faultstring>XML parse failed to build a document from > bytes</faultstring> > </soapenv:Fault> > </soapenv:Body> > </soapenv:Envelope> > > > ***************************************************************************************************** > > Regards > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
