axis2_dep_engine_load_client exits with the env status to AXIS2FAILURE

Function 'axis2_dep_engine_add_new_module' calls 'axis2_dep_engine_load_module_dll' which in turn calls 'axis2_module_desc_add_param'. This function calls 'axis2_module_desc_is_param_locked' which set the env status to AXIS2FAILURE if the module has no parent. But in that case the module parent is only set at the end of 'axis2_dep_engine_add_new_module' by the call of 'axis2_conf_add_module'.

Is that clear ?

Problem is usualy concealed by the AXIS2_PARAM_CHECK macro which reset the env status ! But some days ago the macro was temporaly modified to not reset the env status when param is OK (which seems the good way).