I have what seems to be a problem with send DIME attachments in SOAP. Mime works just fine for me when I use the following to set the send type: reply.getAttachmentsImpl().setSendType(Attachments.SEND_TYPE_MIME).
However, when I make the simple modification to the line above to use DIME as the send type (replace Attachments.SEND_TYPE_MIME with Attachments.SEND_TYPE_DIME), it doesn't work. Is there anything additional that I have to do aside from setting the attachment type to DIME to switch between a MIME and DIME attachment type? I am viewing the request/response through Axis' TCP Tunnel viewer. When I run through a request with DIME, the response from the server looks like this: ------------------------ HTTP/1.1 200 OK Set-Cookie: JSESSIONID=754354ADC18D3D950CEACF80F0191805; Path=/bind Content-Type: application/dime;charset=utf-8 Date: Mon, 28 Feb 2005 20:50:51 GMT Server: Apache-Coyote/1.1 Connection: close "xsd:int">1</totalRecordsFound> <records xsi:type="xsd:string">see attachment</records> <query xsi:type="xsd:string">(+(+RecordType:(interaction complex pathway ) +(gi:(4757840 )))) -((+BINDInteraction.a.type:"not specified" +BINDInteraction.a.shortlabel:"Unknown") (+BINDInteraction.b.type:"not specified" +BINDInteraction.b.shortlabel:"Unknown"))</query> <returnType xsi:type="xsd:string">xml</returnType> </multiRef> </soapenv:Body> </soapenv:Envelope> ------------------------ As you can see it seems as if the response is malformed. Not sure if this is a result of the problem, or something wrong with the proxy that I am using to view the response. It is stumping me because MIME works fine, and DIME give me the weird result above. No exceptions seem to be thrown from the SOAP server. Has anyone else had a problem like this or know how I might troubleshoot it?
