Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 30075 invoked from network); 31 Jan 2006 20:37:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 Jan 2006 20:37:50 -0000 Received: (qmail 40942 invoked by uid 500); 31 Jan 2006 20:37:50 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 40924 invoked by uid 500); 31 Jan 2006 20:37:50 -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 40913 invoked by uid 99); 31 Jan 2006 20:37:50 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2006 12:37:50 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates 66.249.82.203 as permitted sender) Received: from [66.249.82.203] (HELO xproxy.gmail.com) (66.249.82.203) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2006 12:37:49 -0800 Received: by xproxy.gmail.com with SMTP id t16so898229wxc for ; Tue, 31 Jan 2006 12:37:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ERkhn1mp9HnPHLUcoiURZ7F/gjlOv6NFKjYh3EIc67cP8gg1bKN+RaUdj359HXrXb+pnuOUjkg2LFoldPrigGX/CgDnDdjmxRRxk+375QombgIwOWsygd+ywihme4HzcCRUuNuiV532n/TwJwu/E3QOYPz+BnuftXyJfMva4/oA= Received: by 10.11.98.44 with SMTP id v44mr98058cwb; Tue, 31 Jan 2006 12:37:28 -0800 (PST) Received: by 10.11.120.58 with HTTP; Tue, 31 Jan 2006 12:37:28 -0800 (PST) Message-ID: <19e0530f0601311237sdad1ce3l94768269f58a3b4f@mail.gmail.com> Date: Tue, 31 Jan 2006 15:37:28 -0500 From: Davanum Srinivas Reply-To: dims@apache.org To: Apache AXIS C Developers List Subject: Re: guththila re-entrance In-Reply-To: <3d3e8b800601311211na6882b9x@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <3d3e8b800601260613s5b8fa9bcx@mail.gmail.com> <3d3e8b800601260627q18ae3349p@mail.gmail.com> <1138584786.8239.6.camel@localhost.localdomain> <3d3e8b800601311211na6882b9x@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Ed, You have commit privs. Can u please check in the code yourself? :) thanks, dims On 1/31/06, Edward Slattery wrote: > OK, Im now on axis-c-dev. I found some difficulties in building patches, = so > I have logged this and 3 other problems on JIRA with details of the chang= es > needed. > I tried to attach patches, but was unable to attach files - some security > issue that I need to work out. > I have two other fixes to apply yet, which are compiler warnings for > signed/unsigned etc. And one bad return value. > Question about patches- suppose I want to provide patch files for all six= of > my fixes - I guess I cant build one huge patch as that doesnt help you > decide what to apply - but I also cant apply patch after patch unless you > know the exact order to apply them - whats the protocol here? > One big patch with comments showing which parts apply to which problem, o= r > an ordered sequence of patches? > > > > On 30/01/06, Sanjiva Weerawarana wrote: > > Hi Ed, > > > > This would be a *very* useful update! Please go ahead and patch it ... > > > > BTW this discussion belongs in axis-c-dev and not here. > > > > Thanks, > > > > Sanjiva. > > > > On Thu, 2006-01-26 at 14:27 +0000, Edward Slattery wrote: > > > > > > > > > I dont know where to log this one - anyone want to tell me if its a > > > problem or I am doing something wrong? > > > > > > I am testing the Guththila parser, and have a WSDL which contains an > > > of an XSD. > > > > > > I have one single guththila environment, and create a new parser for > > > each file encountered. > > > > > > Guththilla cannot handle that because guththila_event is global, and > > > the inner parse fails because of handling the wrong event > > > type (the GUTHTHILA_EMPTY_ELEMENT from the outer parse.) > > > > > > By putting the guththila_event inside the parser structure, and > > > replacing every occurence (18 in all) of guththila_event with > > > parser->guththila_event, I can successfully re-enter and parse nested > > > files. > > > > > > Would that be a useful update? > > > > > > -- Davanum Srinivas : http://wso2.com/blogs/