[wsf-c-dev] sandesha2/php build with new changes to axis2c

Damitha Kumarage damitha at wso2.com
Fri Apr 13 20:31:33 PDT 2007


I updated and tested sandesha2c code to reflect the new changes to 
axis2c in linux. However following points need to be addressed before I 
commit it.

1. In phase_resolver.c's axis2_phase_resolver_engage_module_to_svc function
    I can see a new change has added that if the module is already 
engaged it returns
    AXIS2_FAILURE. But when I run sandesha2 samples it always fails 
because of this.
    If I don't engage module from my client then also it fails. So 
temporarily I changed
    it to return AXIS2_SUCCESS even if module is already engaged.

2. When I run the second message in the sequence it segfaults at
    axis2_op_client_add_msg_ctx function when it do 
axis2_msg_ctx_free(in_msg_ctx, env);
    The problem is in freeing the AXIS2_TRANSPORT_IN property. I 
temporarily commented
    this line to make it work. Need to find a solution for this.

3. the error model in sandesha2c was to overriede the fuctions of 
axis2_error. But since the
    ops structure was removed from axis2_error now this is impossible. 
As a solution to this
    I moved the
    const axis2_char_t* axutil_error_messages[AXIS2_ERROR_LAST + 10000];
    from error.c t axutil_error.h with the change of increasing the size 
by 10000.
    The idea is to reserve this additional space for error messages in 
axis2c modules.
    For example in sandesha2c module i use the area AXIS2_ERROR_LAST + 
1000 to
    AXIS2_ERROR_LAST + 2000 for sandesha2c error messages. Of course 
this should
    be properly documented.

Damitha




More information about the Wsf-c-dev mailing list