Return-Path: Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 56615 invoked by uid 500); 4 Jul 2003 11:01:06 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 56602 invoked from network); 4 Jul 2003 11:01:05 -0000 Message-ID: <000801c3421b$90a49040$c300000a@caliente> From: "Eric Jain" To: References: Subject: Re: MIME and DIME Date: Fri, 4 Jul 2003 13:01:05 +0200 Organization: Swiss Institute of Bioinformatics MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N RE: MIME and DIME> MessageContext msgContext = MessageContext.getCurrentContext(); > Message response = msgContext.getResponseMessage(); > response.getAttachmentsImpl().setSendType( > > org.apache.axis.attachments.Attachments.SEND_TYPE_DIME); > > response.addAttachmentPart(response.createAttachmentPart( > new DataHandler(new > FileDataSource(tempFile)))); Thanks, this solves one half of the problem :-) > However, I'm not sure that it is possible to determine which type a > client supports, and thus change the attachment format based on that. This would be important. Does anyone know how to detect .NET clients? Maybe through an HTTP header value? If not, we will have to require a custom SOAP header to be set that specifies the expected attachment type. Ugly... -- Eric Jain