I too agree that 1st approach will give us trouble when/if neethi/c will be moving out of the axis2/c project. But considering that we don't plan to move neethi/c out of axis2/c for the moment and considering the problem with initializing the error codes array I am also +1 for the 1st approach.
-sahan On 7/13/07, Samisa Abeysinghe <[EMAIL PROTECTED]> 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 ? Samisa... > thanks, > Dinesh > -- Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
