Hi Samisa, Thank you very much for the tip - it works!,
however it seems to me that the error message "NULL paramater was passed when a non NULL parameter was expected" does not look informative as desirable. Best regards, Leonid Samisa Abeysinghe-2 wrote: > > Krankurs Leonid wrote: >> Hi, >> >> Could you please clarify Axis2c, 0.94 error processing behavior in the >> following scenario: >> >> >> axis2_allocator_t* allocator = axis2_allocator_init (NULL); >> axis2_error_t* error = axis2_error_create(allocator); >> axis2_env_t* env = axis2_env_create_with_error(allocator, error); >> > calll axis2_error_init(); after creating the error. It is a bug that is > is not called from axis2_env_create_with_error, but you can call it > yourself for the time being. >> both calls >> AXIS2_ERROR_GET_MESSAGE(env->error) >> env->error->ops->get_extended_message(env->error) >> return NULL >> >> what is wrong? >> > This would go away, if you call the axis2_error_init(); function. Please > raise a Jira for this. > > Another alternative is to call > axis2_env_create_all() to create the environment. That calls > axis2_error_init(); > > Samisa... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Axis2c%2C-0.94%2C-error-processing-tf2443488.html#a6822733 Sent from the Axis - C++ - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
