+1 on having a naming scheme that signifies API vs internal. Kind of painfully long tho!PaulOn 11/4/05, Sanjiva Weerawarana <
[EMAIL PROTECTED]> wrote:On Thu, 2005-11-03 at 11:41 +0600, Damitha Kumarage wrote:
> I'll further added> axis2_environment_create (allocator)>which
On Thu, 2005-11-03 at 11:41 +0600, Damitha Kumarage wrote:
> I'll further added
> axis2_environment_create (allocator)
>which is not supposed to be used by Axis2 users. This is used
> only to create the default environment
If its not meant to be used by users, should we f
nandika jayawardana wrote:
Hi all,
Adding a macro to check the environment null condition in the
axis2_environment.h will be useful in writing code , This macro would
be like AXIS2_ENV_CHECK(env,error_return) , which will check the env
passed and create a default environment if the environm
Hi all,
Adding a macro to check the environment null condition in the
axis2_environment.h will be useful in writing code , This macro would
be like AXIS2_ENV_CHECK(env,error_return) , which will check the env
passed and create a default environment if the environment is null and
then set error co
Samisa Abeysinghe wrote:
Damitha Kumarage wrote:
Hi all,
I have done some changes to axis2_enviroment_t. Please read and give
your
comments.
Currently we are facing following problems with the environment
1. Currently some functions return axis2_status_t (status code)
and some other
Damitha Kumarage wrote:
Hi all,
I have done some changes to axis2_enviroment_t. Please read and give your
comments.
Currently we are facing following problems with the environment
1. Currently some functions return axis2_status_t (status code)
and some other return types.
We need
Hi all,
I have done some changes to axis2_enviroment_t. Please read and give your
comments.
Currently we are facing following problems with the environment
1. Currently some functions return axis2_status_t (status code) and
some other return types.
We need a conventions as to which