Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 18623 invoked from network); 15 Jul 2007 05:32:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jul 2007 05:32:15 -0000 Received: (qmail 79231 invoked by uid 500); 15 Jul 2007 05:32:17 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 79197 invoked by uid 500); 15 Jul 2007 05:32:17 -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 79185 invoked by uid 99); 15 Jul 2007 05:32:17 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jul 2007 22:32:17 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of nabeel.yoosuf@gmail.com designates 209.85.146.180 as permitted sender) Received: from [209.85.146.180] (HELO wa-out-1112.google.com) (209.85.146.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jul 2007 22:32:13 -0700 Received: by wa-out-1112.google.com with SMTP id k22so1272527waf for ; Sat, 14 Jul 2007 22:31:53 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=fGXGTWNQdEUyCvPuDGyRdnCRnUAhBHb7jakOB3pS1pv7gTpnyFdQeJ5f5G1sZWkX2fAuAmP1A0/fP0a+VEotRk3AYyJOAgL/ycIOrnxD94fvce1IeS9caHarNobztBE0NK6CxfG/AfnfWc9jsM4yzRBjlwAHJQNzwLyuYurMNFs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=t4BJGSYqI5OfLgb1WHn7sCDo57kw+xbBdcICoDTdW9rMM12msWLr1E81mj98Vl6wZfrvvOAvF2fPAh12J1ToYh2pGiVhr7TFlomJBrf9wvivN1ZituPwe8efl6FnahoPjy3ZMS54B5IGlgD76yjdcN7XAtMTSU16YuJRjqLDcYo= Received: by 10.115.58.1 with SMTP id l1mr3025781wak.1184477512950; Sat, 14 Jul 2007 22:31:52 -0700 (PDT) Received: by 10.114.160.17 with HTTP; Sat, 14 Jul 2007 22:31:52 -0700 (PDT) Message-ID: Date: Sun, 15 Jul 2007 11:01:52 +0530 From: "Nabeel Yoosuf" To: "Apache AXIS C Developers List" Subject: Re: Error handling in Neethi/C In-Reply-To: <1184307411.12527.7.camel@manjula-laptop> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_37611_13372221.1184477512925" References: <1184301958.8193.13.camel@manjula-laptop> <873azskgze.fsf@etch.wso2.com> <46970846.5020909@wso2.com> <1184307411.12527.7.camel@manjula-laptop> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_37611_13372221.1184477512925 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 7/13/07, manjula wrote: > > On Fri, 2007-07-13 at 11:06 +0600, Samisa Abeysinghe wrote: > > Dinesh Premalal wrote: > > > manjula writes: > > > > > >> There are two approaches for Error handling in Neethi/C > > >> > > >> 1. To add error codes to current Axis2/C error.h and use those inside > > >> Neethi/C > > >> > > >> 2. Adding separate error codes as in sandesha2/c and use them inside > > >> Neethi/C > > >> > > > > > > +1 for first approach. > > > > > hmmm would not second approach be more leaner ? > > The problem is when to init the error struct which has error codes. > Because there is nothing like module init in policy. Policy functions > can be called from any where. > > -Manjula. The second option would pay off in the long run. One way to achieve this is to get rid of axutil_error_init function; you can statically define error-no - error-str mapping during compile time. Nabeel. --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-c-dev-help@ws.apache.org > > -- http://www.cs.purdue.edu http://mohamednabeel.blogspot.com ------=_Part_37611_13372221.1184477512925 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 7/13/07, manjula <manjula@wso2.com> wrote:
On Fri, 2007-07-13 at 11:06 +0600, Samisa Abeysinghe wrote:
> Dinesh Premalal wrote:
> > manjula <manjula@wso2.com> writes:
> >
> >> There are two approaches for Error handling in Neethi/C
> >>
> >> 1. To add error codes to current Axis2/C error.h and use those inside
> >> Neethi/C
> >>
> >> 2. Adding separate error codes as in sandesha2/c and use them inside
> >> Neethi/C
> >>
> >
> > +1 for first approach.
> >
> hmmm would not second approach be more leaner ?

The problem is when to init the error struct which has error codes.
Because there is nothing like module init in policy. Policy functions
can be called from any where.

-Manjula.


The second option would pay off in the long run. One way to achieve this is to get rid of axutil_error_init function; you can statically define error-no - error-str mapping during compile time.

Nabeel.

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org




--
http://www.cs.purdue.edu
http://mohamednabeel.blogspot.com ------=_Part_37611_13372221.1184477512925--