Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 32605 invoked from network); 17 Jul 2006 07:14:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Jul 2006 07:14:26 -0000 Received: (qmail 46458 invoked by uid 500); 17 Jul 2006 07:14:25 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 46442 invoked by uid 500); 17 Jul 2006 07:14:25 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 46431 invoked by uid 99); 17 Jul 2006 07:14:25 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 00:14:25 -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 samisa.abeysinghe@gmail.com designates 64.233.162.195 as permitted sender) Received: from [64.233.162.195] (HELO nz-out-0102.google.com) (64.233.162.195) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 00:14:16 -0700 Received: by nz-out-0102.google.com with SMTP id l8so574669nzf for ; Mon, 17 Jul 2006 00:13:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=A3cAzUCSu7D2j2pb5eARjNQ2jPirOxFfqIyeyEqs2oGJAK6qP5U3QJBEe9AwqqEaD5/wf49RTba3JBj3rqKG/CvwbTp+z3YCoolwVscPzf2o7BsEmcm0kOpjL04aC04P4cYyC1lii2kTL7KABRcj0OH8M94+KC3vCYQfdsZem0E= Received: by 10.36.19.4 with SMTP id 4mr2396002nzs; Mon, 17 Jul 2006 00:13:50 -0700 (PDT) Received: from ?192.168.1.151? ( [222.165.173.179]) by mx.gmail.com with ESMTP id 39sm723811nzk.2006.07.17.00.13.47; Mon, 17 Jul 2006 00:13:49 -0700 (PDT) Message-ID: <44BB389B.4000106@gmail.com> Date: Mon, 17 Jul 2006 12:43:31 +0530 From: Samisa Abeysinghe User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Apache AXIS C Developers List Subject: [Axis2] Soap builder next problems References: <002701c6a847$6021f3a0$346a080a@SoftVotes2> In-Reply-To: <002701c6a847$6021f3a0$346a080a@SoftVotes2> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 Hi All, In case of handling MTOM, what we basically do is to get the MIME parts from the stream and build a binary data map and set that map to SOAP builder. The SOAP builder is supposed to look into this binary data map and attach the relevant data handlers to the correct places when building the SOAP body. However, given that we do not have the luxury of polymorphism enjoyed by Java implementation, our OM and SOAP 'next' mechanisms are different. In most of the cases what the users does is to access the base node from SOAP body and then onwards pull the om tree, in which case, SOAP builder's next is not called. Hence we miss the binary parts. I worked around this to call 'has fault' check, in case we have mtom. Has fault seem to build the hole SOAP body by mistake (so there is a bug as well). But I used this bug to ensure the data handlers are attached in the correct place. We need to fix these issues. Thanks, Samisa... --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-dev-help@ws.apache.org