Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 44096 invoked from network); 31 Mar 2006 13:50:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 Mar 2006 13:50:17 -0000 Received: (qmail 95004 invoked by uid 500); 31 Mar 2006 13:50:14 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 94963 invoked by uid 500); 31 Mar 2006 13:50:14 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 94952 invoked by uid 99); 31 Mar 2006 13:50:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Mar 2006 05:50:14 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [209.68.5.16] (HELO relay02.pair.com) (209.68.5.16) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 31 Mar 2006 05:50:13 -0800 Received: (qmail 37795 invoked from network); 31 Mar 2006 13:49:50 -0000 Received: from unknown (HELO ?10.71.0.121?) (unknown) by unknown with SMTP; 31 Mar 2006 13:49:50 -0000 X-pair-Authenticated: 68.166.35.68 Subject: Re: [Axis2] Data binding attachments support (was: CHAT LOG : 2006-03-29) From: Sanjiva Weerawarana To: axis-dev@ws.apache.org Cc: Kohsuke.Kawaguchi@sun.com In-Reply-To: References: <442B6149.2050104@thoughtcraft.com> <442B6C40.2060405@sosnoski.com> Content-Type: text/plain Organization: Lanka Software Foundation Date: Fri, 31 Mar 2006 19:49:31 +0600 Message-Id: <1143812971.8353.27.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Fri, 2006-03-31 at 15:35 +0600, Thilina Gunarathne wrote: > > What we want is a "thingy" which can be stored away and LATER used to > get the real attachment data after all XML pulling is done > > > IMHO we are doing the exactly the same thing using OMTexts.. Currently > we are doing this with more flexibility and of course with a catch.. > Flexibility is given by allowing the users to get the real attachment > data if they wish while pulling the XML.. Catch is that we are > buffering the SOAP Envelope in the MIME Parser which is underneath the > StaxReader... Thilina, I don't see this as a catch - isn't it impossible to get to any attachments without buffering the SOAP envelope? Or are you thinking about reading the SOAP envelope and buffering it IFF someone actually refers to an attachment? While that's interesting in theory, whoever sent the attachment more often than not expected the other end to read the darn thing. I don't see the point of that potential optimization. Maybe I'm missing something. Sanjiva.