Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 70613 invoked from network); 19 Sep 2006 20:29:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Sep 2006 20:29:51 -0000 Received: (qmail 1905 invoked by uid 500); 19 Sep 2006 20:29:27 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 1864 invoked by uid 500); 19 Sep 2006 20:29:27 -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: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 1759 invoked by uid 99); 19 Sep 2006 20:29:27 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Sep 2006 13:29:26 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=csethil@gmail.com; domainkeys=good X-ASF-Spam-Status: No, hits=0.4 required=5.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from ([64.233.182.190:10829] helo=nf-out-0910.google.com) by idunn.apache.osuosl.org (ecelerity 2.1 r(10620)) with ESMTP id D2/7A-28275-32350154 for ; Tue, 19 Sep 2006 13:29:23 -0700 Received: by nf-out-0910.google.com with SMTP id x29so248386nfb for ; Tue, 19 Sep 2006 13:29:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ah0FMlynbWC8fHE3lu78kpeNd8KohNDbm7i27xPr5pae+ew/SyEzy3vJ7TExAmOWqbrwJxdDWWDX/RMleveVjEdVvKlS+FJp4kPP37vd0tOBVlXHDirRrVPBq7sCrmFjLYtGGkU4puFs7yP6xu639LyIxN+zbze45IDlglxNylk= Received: by 10.49.90.4 with SMTP id s4mr18830086nfl; Tue, 19 Sep 2006 13:29:17 -0700 (PDT) Received: by 10.49.63.16 with HTTP; Tue, 19 Sep 2006 13:29:17 -0700 (PDT) Message-ID: Date: Wed, 20 Sep 2006 02:29:17 +0600 From: "Thilina Gunarathne" To: axis-user@ws.apache.org, dims@apache.org Subject: Re: Setting the Content-ID header for an MTOM attachment In-Reply-To: <19e0530f0609191305p629faf7dw7b54db66370ad6c6@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <19e0530f0609191305p629faf7dw7b54db66370ad6c6@mail.gmail.com> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Yes.. Possible.. He can do it at the client (using OperationClient) program as well as at the service impl too :).... Then he'll be using Soap With Attachments.. Not MTOM... Thanks, ~Thilina On 9/20/06, Davanum Srinivas wrote: > Thilina, > > Can Yoram write a custom handler, get access to the message context > and use the following method in MessageContext to set a custom > attachment? > > public void addAttachment(String contentID, DataHandler dataHandler) > > -- dims > > On 9/19/06, Yoram Givon wrote: > > > > The reason I need to set the content-ID is that the Transcoding > > web-service uses the content-id header to identify the attached content. > > When the MTOM engine generates the content-id for me, there is no way > > for me to tell the web service where the content is. > > > > When I used axis 1.4 for the same goal I just added an AttachmentPart > > and then set the setConentID for it. > > > > I was just not able to find the equivalent way to do it with Axis2. > > > > Cheers, > > Yoram > > > > -----Original Message----- > > From: Thilina Gunarathne [mailto:csethil@gmail.com] > > Sent: Tuesday, September 19, 2006 12:05 PM > > To: axis-user@ws.apache.org > > Subject: Re: Setting the Content-ID header for an MTOM attachment > > > > Hi Yoram, > > You can use the OMText.getContentId() to request the content id, > > given that OMText object contains the binary attachment you want to > > send. > > > > What is you use case..When using MTOM Axis2 will take care of putting > > the content-id in to the SOAP request appropriately according to the > > specification, so that the server knows where the attachment is. I > > don't see why somebody needs to access the content-id manually. > > > > ~Thilina > > > > On 9/19/06, Yoram Givon wrote: > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > I am using Axis2 to create a SOAP request to a web service which > > performs > > > Transcoding of a file I attached to the SOAP message using MTOM. > > > > > > > > > > > > My only problem is that I also have to pass the content-id of the > > attachment > > > as part of the SOAP request so the server will know where the file is. > > > > > > > > > > > > I have searched through the mailing list and the internet and was not > > able > > > so far to find a method to set the content-id header for an MTOM > > attachment. > > > > > > > > > > > > Does any one know if there is a way to set the content-id header of an > > MTOM > > > attachment? > > > > > > > > > > > > Cheers, > > > > > > > > > > > > Yoram > > > > > > -- > > http://webservices.apache.org/~thilina/ > > http://thilinag.blogspot.com/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > > For additional commands, e-mail: axis-user-help@ws.apache.org > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > > For additional commands, e-mail: axis-user-help@ws.apache.org > > > > > > > -- > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-user-help@ws.apache.org