On 7/13/07, manjula <[EMAIL PROTECTED]> wrote:
On Fri, 2007-07-13 at 11:06 +0600, Samisa Abeysinghe wrote: > Dinesh Premalal wrote: > > manjula <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://www.cs.purdue.edu http://mohamednabeel.blogspot.com
