Re: Doc/Lit webservice generating wrong SOAP response

[Dan Weston]

Chunked encoding of the response, very common, and shouldn't be a  
problem unless the toolkit receiving the response is really dumb.

On Monday, March 24, 2003, at 10:42 PM, Davinder Singh wrote:

Hi,
I have developed a document/literal webservice which generates the  
following response when called by a .NET client:

HTTP/1.1 100 Continue�
HTTP/1.1 200 OK
Date: Tue, 25 Mar 2003 06:20:09 GMT
Server: WebLogic WebLogic Server 7.0 SP1� Mon Sep 9 22:46:58 PDT 2002  
206753�
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: Chunked�

01c4
<?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:Body>
� <StartMonitoringResponse  
xmlns="http://www.aspect.com/ECS/ECSAdapterServices";>
��  
<StartMonitoringResult>1,AgentMonitorCrossRefId</> StartMonitoringResult>
� </StartMonitoringResponse>
�</soapenv:Body>
</soapenv:Envelope>
0000

Please note "01c4" in the beginning of the SOAP message and "0000" at  
the end of it. Any idea why these are being added?

Any suggestion would be helpful.

Thanx,
davin