Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 5011 invoked from network); 7 Sep 2006 05:07:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Sep 2006 05:07:20 -0000 Received: (qmail 28257 invoked by uid 500); 7 Sep 2006 05:07:12 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 28039 invoked by uid 500); 7 Sep 2006 05:07:12 -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 28028 invoked by uid 99); 7 Sep 2006 05:07:11 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Sep 2006 22:07:11 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of csethil@gmail.com designates 64.233.182.189 as permitted sender) Received: from [64.233.182.189] (HELO nf-out-0910.google.com) (64.233.182.189) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Sep 2006 22:07:11 -0700 Received: by nf-out-0910.google.com with SMTP id x29so348101nfb for ; Wed, 06 Sep 2006 22:06:49 -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=liBY4akRz9qd16vHXpXtoAiDy2hcGOqIoM+hfzI2PDPFrFq4wjh5Ff+4DONin599t0mO620wMBXagg8tmIL09k6kgivBVh+PM6yEuFD7fLYModLu9+qFlVOAckq5LFhbl4qU7iD7K2L2eTR9o04cTULEZjz3dFVQBhSx/lXLnC4= Received: by 10.49.8.10 with SMTP id l10mr2044405nfi; Wed, 06 Sep 2006 22:06:49 -0700 (PDT) Received: by 10.49.63.16 with HTTP; Wed, 6 Sep 2006 22:06:49 -0700 (PDT) Message-ID: Date: Thu, 7 Sep 2006 10:36:49 +0530 From: "Thilina Gunarathne" To: axis-user@ws.apache.org Subject: Re: Re: MTOM attachments from XFire In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <19e0530f0609061816u3a9520e0xf94a6a1958b669ab@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Jay, >> The web site says clients automatically handle MTOM >>attachments... Yes.. It's true.. Client identifies and creates a OMText object in the place of XOP:Include element... Configuration Dims has mentioned is usefull when sending MTOM attachements. What's the data binding framework you are using.. XMLBeans or ADB.. Please post your WSDL and if possible message snapshots too... Thilina On 9/7/06, Jay Gillibrand wrote: > I tried the nightly and had two problems. First, one of the methods in > the stub wouldn't even compile since it was filled with mismatched ifs > and elses. Since it wasn't related to the download method I'm calling, > I just commented it out for now. > > Second, the stub for the download method still didn't work--but it was > close. My Soap response payload looks kinds like (wrapped > doc-literal): > > > > > ... > > The generated stub gets to the "contents" element and checks if it is > text or an "Include" element. It's neither, so it exceptions right > there. If I edit the stub to include an extra call to read.next() to > skip the "contents" element, it then finds the "Include" and > everything handles the response as expected: the file is downloaded. > > Basically it seems like the code generator in 1.0 can't generate stubs > for MTOM at all. The nightly build is getting closer it, but still > produces unusable code without a lot of tweaking. Anything I'm > missing? Does Axis 1 handle MTOM? > > -Jay > > > On 9/6/06, Davanum Srinivas wrote: > > Please use a nightly build of Axis2. > > > > Options options = myStub._getServiceClient().getOptions(); > > options.setProperty(org.apache.axis2.Constants.Configuration.ENABLE_MTOM, > > Boolean.TRUE); > > > > -- dims > > > > On 9/6/06, Jay Gillibrand wrote: > > > I'm calling an XFire based web service that is using MTOM to return > > > attachments. Tracing the actual HTTP request I can see the response > > > looks like what I'd expect, but Axis2 fails to parse the results. > > > > > > The problem _seems_ to be that my Axis2 client stubs are expecting the > > > attachments to be inlined as base 64 in the Soap envelope, that is, > > > they are looking for a text element under the > > > element in the response. The actual response has an > > > element there that refers to the data in another MIME section. > > > > > > Is there something that I need to do to get the stubs to recongnize > > > MTOM attachments? The stubs appear to be completely ignorant of MTOM > > > right now. The web site says clients automatically handle MTOM > > > attachments... > > > > > > -Jay > > > > > > --------------------------------------------------------------------- > > > 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 > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > -- "May the SourcE be with u" http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina --------------------------------------------------------------------- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-user-help@ws.apache.org