I did try it with MTOM enabled too and got the same (equivalent)
result... an empty document (see below). Not sure what other workarounds
are available to me. Thanks

>From SOAPMonitor...
<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
  <soapenv:Header />
  <soapenv:Body>
    <ns1:getDocumentResponse xmlns:ns1="urn:webservices.docharbor.com">
      <ns1:return>
        <ns1:documentSize>198</ns1:documentSize>
 
<ns1:document>e1xydGYxXGFuc2lcYW5zaWNwZzEyNTJcZGVmZjBcZGVmbGFuZzEwMzN7XG
ZvbnR0Ymx7XGYwXGZzd2lzc1xmY2hhcnNldDAgQXJpYWw7fX0NCntcKlxnZW5lcmF0b3IgTX
NmdGVkaXQgNS40MS4xNS4xNTA3O31cdmlld2tpbmQ0XHVjMVxwYXJkXGYwXGZzMjAgSSdtIH
RoZSBkZWZhdWx0IGRvY3VtZW50IGZvciBpbXBvcnRhdGlvbi5ccGFyDQp9DQoA</ns1:docu
ment>
      </ns1:return>
    </ns1:getDocumentResponse>
  </soapenv:Body>
</soapenv:Envelope>


>From tcpmon
HTTP/1.1 200 OK
Server: ""
Date: Tue, 27 Mar 2007 13:30:16 GMT
Content-type: multipart/related;
boundary=MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495;
type="application/xop+xml";
start="<0.urn:uuid:[EMAIL PROTECTED]>";
start-info="text/xml"; charset=UTF-8Transfer-encoding:
chunked02d7--MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495content
-type: application/xop+xml; charset=UTF-8;
type="text/xml";content-transfer-encoding: binarycontent-id: 
   <0.urn:uuid:[EMAIL PROTECTED]>
      <?xml version='1.0' encoding='UTF-8'?>
         <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
            <soapenv:Header />
            <soapenv:Body>
               <ns1:getDocumentResponse
xmlns:ns1="urn:webservices.docharbor.com">
                  <ns1:return>
                     <ns1:documentSize>198</ns1:documentSize>
                     <ns1:document>
                        <xop:Include
href="cid:1.urn:uuid:[EMAIL PROTECTED]"
xmlns:xop="http://www.w3.org/2004/08/xop/include"; />
                     </ns1:document>
                  </ns1:return>
               </ns1:getDocumentResponse>
            </soapenv:Body>
         </soapenv:Envelope>
00cc

--MIMEBoundaryurn_uuid_E612E8E634E97EAEE61175002216495
content-type: application/octet-stream
content-transfer-encoding: binary
content-id: 
         <1.urn:uuid:[EMAIL PROTECTED]>0


-----Original Message-----
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 27, 2007 5:54 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 not putting binary attachment on the wire

Opps... Sounds like a bug to me.. Please log a JIRA with more details..
Some source code would be actually better...

Then in order to get through this you can try enablingMTOM in your
Axis2.xml..

Thanks,
Thilina

On 3/28/07, Masin, Valerie <[EMAIL PROTECTED]> wrote:
>
>
> My webservice returns a binary document which I declare in my wsdl as 
> base64Binary. Using SOAPMonitor I see my document in the returned soap

> message. However, tcpmon shows that the document is empty. I have 
> tried this both with and without MTOM.
>
> Without MTOM here is the soap from SOAPMonitor...
> <?xml version='1.0' encoding='utf-8'?> <soapenv:Envelope 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   <soapenv:Header />
>   <soapenv:Body>
>     <ns1:getDocumentResponse
xmlns:ns1="urn:webservices.docharbor.com">
>       <ns1:return>
>         <ns1:documentSize>198</ns1:documentSize>
>
>
<ns1:document>e1xydGYxXGFuc2lcYW5zaWNwZzEyNTJcZGVmZjBcZGVmbGFuZzEwMzN7XG
ZvbnR0Ymx7XGYwXGZzd2lzc1xmY2hhcnNldDAgQXJpYWw7fX0NCntcKlxnZW5lcmF0b3IgTX
NmdGVkaXQgNS40MS4xNS4xNTA3O31cdmlld2tpbmQ0XHVjMVxwYXJkXGYwXGZzMjAgSSdtIH
RoZSBkZWZhdWx0IGRvY3VtZW50IGZvciBpbXBvcnRhdGlvbi5ccGFyDQp9DQoA</ns1:docu
ment>
>       </ns1:return>
>     </ns1:getDocumentResponse>
>   </soapenv:Body>
> </soapenv:Envelope>
>
>
> ... and here is the output of tcpmon
> HTTP/1.1 200 OK
> Server: ""
> Date: Tue, 27 Mar 2007 18:26:12 GMT
> Content-type: text/xml; charset=UTF-8
> Transfer-encoding: chunked
>
> 016f
> <?xml version='1.0' encoding='UTF-8'?>
>    <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>       <soapenv:Header />
>       <soapenv:Body>
>          <ns1:getDocumentResponse
xmlns:ns1="urn:webservices.docharbor.com">
>             <ns1:return>
>                <ns1:documentSize>198</ns1:documentSize>
>                <ns1:document></ns1:document> <<<<<<<<<<<<<<<<<<<< 
> notice the empty document
>             </ns1:return>
>          </ns1:getDocumentResponse>
>       </soapenv:Body>
>    </soapenv:Envelope>
> 0
>
> Does anyone know why this is happening? Thanks, Valerie


--
Thilina Gunarathne  -  http://www.wso2.com -
http://thilinag.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to