In case anyone cares, I solved this (and my earlier post about client blocking in socketWrite() ) by getting a new reference to the service through the ServiceLocator. Maybe that's the way you're supposed to do it and I missed that part...

Linus Kamb wrote:
Why would Axis1 post a request as an attachment?

My service returns documents as attachments. The first request goes out as a normally-formatted soap request. Subsequent requests, however, put the soap message in to an attachment, as follows. Also, it appears to be attaching the prior response attachment on to the request. (Unless that is a tcpmon artifact.)

POST /axis/services/SPADE_QueryService HTTP/1.0

Content-Type: multipart/related; type="text/xml"; start="<BC12686C70134DE6BB8177E11F2132B3>"; boundary="----=_Part_0_7501974.1201725644209"
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: usra2:8082
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 307178

------=_Part_0_7501974.1201725644209
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-Id: <BC12686C70134DE6BB8177E11F2132B3>
   <?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>
            <getProduct xmlns="http://www.iris.edu/spade";>
               <productId>
<ProductType name="RecordSection" uri="http://www.iris.edu/xml/recordsection"/> <ProductId>20080106_051417.2.spyder._US-ALL.TELE_LONG</ProductId>
                  <SourceId>IRIS_DMC</SourceId>
               </productId>
               <includeAttachments>true</includeAttachments>
            </getProduct>
         </soapenv:Body>
</soapenv:Envelope>------=_Part_0_7501974.1201725644209Content-Type: application/xmlContent-Transfer-Encoding: binaryContent-Id:
      <8B569B94D4D794855F8B2DED839383D9>
         <?xml version="1.0" encoding="UTF-8"?>

---------------------------------------------------------------------
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