The only times I have seen that kind of additional output is when
passing the response through a proxy such as tcpmon.  I know that when
the content gets large the proxy started including additional http
information in the response that caused the response to no longer be
valid.
 
I don't know much about this stuff but perhaps it is  related to http
chunking?  Does the j2me client support http chunking?
 
 

___________________________________________

Gavin Hogan
Programmer/Analyst
The State University of New York
State University Plaza
Albany, NY 12246
Phone 518-443-5481
fax 518-443-5809
e-mail [EMAIL PROTECTED] 

        -----Original Message-----
        From: Dave Shannon [mailto:[EMAIL PROTECTED] 
        Sent: Wednesday, September 05, 2007 4:58 PM
        To: [email protected]
        Subject: [xfire-user] Soap response format
        
        
        I have an xfire deployed web service which I can successfully
call using xfire client, .NET, .NET compact, and j2me using ksoap.  One
method returns audio data.  I typically set up the service for MTOM but
for .NET compact/j2me access I disable since they don't support it.
KSoap complains about the "1c" before </soap:Body> in the following
response.  Can someone explain to me if this is valid in the response
and what it represents?
         
        Regards,
         
        Dave Shannon
         
         
        HTTP/1.1 200 OK
        Content-Type: text/xml; charset=UTF-8
        Content-Language: en-US
        Set-Cookie: JSESSIONID=0000wqb7St_8X83RljOa13hnUwP:-1; Path=/
        Transfer-Encoding: chunked
        Date: Wed, 05 Sep 2007 19:27:16 GMT
        Server: WebSphere Application Server/6.1
        Expires: Thu, 01 Dec 1994 16:00:00 GMT
        Cache-Control: no-cache="set-cookie, set-cookie2"
         
        fd
        <soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/
<http://schemas.xmlsoap.org/soap/envelope/> "
xmlns:xsd="http://www.w3.org/2001/XMLSchema
<http://www.w3.org/2001/XMLSchema> "
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> ">
        <soap:Body
xmlns:ns1="http://www.iperia.com/webservices/vxsa/messaging/v1_0_types/
<http://www.iperia.com/webservices/vxsa/messaging/v1_0_types/> ">
        8000
        <GetMessageAttachmentResponse
xmlns="http://www.iperia.com/webservices/vxsa/messaging/v1_0_types/
<http://www.iperia.com/webservices/vxsa/messaging/v1_0_types/> "
xmlns:xmime="http://www.w3.org/2005/05/xmlmime
<http://www.w3.org/2005/05/xmlmime> ">
          <messageAttachmentCollection>
            <messageAttachment>
              <type>AUDIO</type>
              <data>...a bunch of base64 encoded data...</data>
            </messageAttachment>
          </messageAttachmentCollection>
        </GetMessageAttachmentResponse>
        1c
        </soap:Body>
        </soap:Envelope>
        0
         
        wsdl
        <xsd:complexType name="MessageAttachment">
                            <xsd:sequence>
                   <xsd:element name="type"
type="types:MessageAttachmentType" minOccurs="1" maxOccurs="1"/>
                   <xsd:element name="data" type="xmime:base64Binary"
xmime:expectedContentTypes="application/octet-stream" minOccurs="1"
maxOccurs="1"/>
                           </xsd:sequence>
        </xsd:complexType>

Reply via email to