Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 73613 invoked from network); 17 Jan 2006 19:37:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Jan 2006 19:37:53 -0000 Received: (qmail 74760 invoked by uid 500); 17 Jan 2006 19:37:37 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 73880 invoked by uid 500); 17 Jan 2006 19:37:31 -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 73616 invoked by uid 99); 17 Jan 2006 19:37:30 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jan 2006 11:37:30 -0800 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of csethil@gmail.com designates 66.249.92.200 as permitted sender) Received: from [66.249.92.200] (HELO uproxy.gmail.com) (66.249.92.200) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jan 2006 11:37:28 -0800 Received: by uproxy.gmail.com with SMTP id m2so11906ugc for ; Tue, 17 Jan 2006 11:37:07 -0800 (PST) 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:references; b=VEV44Ibp6IVNYXvZXZlsRvIF3C589+XxybXc6gRN69c4s0g0z5sTgVg8QgJ59wt+lM7xscY3CjvqEpE4/TSncO7GReq8FWBcw/ETX76Jrpo31TnCb9HyRNb7y/F2B962Y37s67lRl82kNcwnHGyattW49VwCJgZxexLqDz1S6iU= Received: by 10.49.40.14 with SMTP id s14mr350524nfj; Tue, 17 Jan 2006 11:37:07 -0800 (PST) Received: by 10.48.241.9 with HTTP; Tue, 17 Jan 2006 11:37:06 -0800 (PST) Message-ID: Date: Wed, 18 Jan 2006 01:37:06 +0600 From: Thilina Gunarathne To: axis-dev@ws.apache.org Subject: Re: [jira] Created: (AXIS2-372) Client API support Attachments (like Axis 1.X) In-Reply-To: <1597590885.1136869161287.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_17455_20150619.1137526626990" References: <1597590885.1136869161287.JavaMail.jira@ajax.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_17455_20150619.1137526626990 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, >>we need streaming support similar to one that was added in Axis 1.3 Can you please explain what you mean by Streaming. Idea is not clear to me... I'm sure a explanation will benefit others as well.. Thanks, ~Thilina On 1/10/06, Davanum Srinivas (JIRA) wrote: > > Client API support Attachments (like Axis 1.X) > ---------------------------------------------- > > Key: AXIS2-372 > URL: http://issues.apache.org/jira/browse/AXIS2-372 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Davanum Srinivas > > > Use case: want to write an intermediary that peeks just the soap > headers and forwards messages with MTOM or SwA attachments. i don't > think our users can implement this with current public API. They would > have to muck around with the internals which can change. Also, we need > streaming support similar to one that was added in Axis 1.3 > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > -- "May the SourcE be with u" http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina ------=_Part_17455_20150619.1137526626990 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi,
>>we need streaming support similar to one that was added in Axi= s 1.3

Can you please explain what you mean by Streaming. Idea is not= clear to me... I'm sure a explanation will benefit others as well..
 
Thanks,
~Thilina

 
On 1/10/06, = Davanum Srinivas (JIRA) <jira@apa= che.org> wrote:
Client API support Attachments (= like Axis 1.X)
----------------------------------------------

&nb= sp;       Key: AXIS2-372
        URL: http://issues.apache.org/jira/brow= se/AXIS2-372
    Project: Apache Axis 2.0 (Axis2= )
       Type: Bug
   Reporte= r: Davanum Srinivas


Use case: want to write an intermediary that peeks just the soapheaders and forwards messages with MTOM or SwA attachments. i don't
thi= nk our users can implement this with current public API. They would
have to muck around with the internals which can change. Also, we need
s= treaming support similar to one that was added in Axis 1.3

--
Thi= s message is automatically generated by JIRA.
-
If you think it was s= ent incorrectly contact one of the administrators:
  http://issues.apache.org/jira/secure/Administrators.jspa
-=
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



--
"May the SourcE be with u"  =           
http://webservices.apache.org/~thi= lina/
http://thilinag.blogspot.= com/           &= nbsp;     http://www.bloglines.com/blog/Thilina     = ;         =20 ------=_Part_17455_20150619.1137526626990--