[
https://issues.apache.org/jira/browse/AXIS2C-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1408.
-------------------------------------
Fix Version/s: 2.0.0
Resolution: Fixed
The fix removes the erroneous AXIS2_ERROR_SET call in
axis2_module_desc_is_param_locked() when the parent is NULL. This was
setting the environment to an error state during normal module
loading, even though the function was returning a valid result
(AXIS2_FALSE - param is not locked).
> axis2_dep_engine_load_client exits with the env status to AXIS2FAILURE
> -----------------------------------------------------------------------
>
> Key: AXIS2C-1408
> URL: https://issues.apache.org/jira/browse/AXIS2C-1408
> Project: Axis2-C
> Issue Type: Bug
> Components: core/deployment
> Reporter: Francois Mireaux
> Priority: Major
> Fix For: 2.0.0
>
>
> 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).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
