You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Damitha Kumarage (JIRA)" <ji...@apache.org> on 2008/03/26 08:55:24 UTC
[jira] Created: (AXIS2C-1086) In function
axis2_op_register_op_ctx() failure is logged and returned in a working
path.
In function axis2_op_register_op_ctx() failure is logged and returned in a working path.
----------------------------------------------------------------------------------------
Key: AXIS2C-1086
URL: https://issues.apache.org/jira/browse/AXIS2C-1086
Project: Axis2-C
Issue Type: Bug
Reporter: Damitha Kumarage
In the following code of axis2_op_register_op_ctx() function
msg_id = axis2_msg_ctx_get_msg_id(msg_ctx, env);
if (!msg_id)
{
AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
"Message id not found for message context while "\
"registering operation context for operation %s", opname);
return AXIS2_FAILURE;
}
When message id is not found in the messages context it is correctly logged as error and returned failure. However every places from which this function called, status is not handled and although error is logged and failure returned still code work successfully. This is behaviour is not acceptable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Resolved: (AXIS2C-1086) In function
axis2_op_register_op_ctx() failure is logged and returned in a working
path.
Posted by "Dinesh Premalal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Premalal resolved AXIS2C-1086.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.3.1
This was happened because of the incorrect sequence of the functions that we called. I fixed this issue and change the log level into warning.
> In function axis2_op_register_op_ctx() failure is logged and returned in a working path.
> ----------------------------------------------------------------------------------------
>
> Key: AXIS2C-1086
> URL: https://issues.apache.org/jira/browse/AXIS2C-1086
> Project: Axis2-C
> Issue Type: Bug
> Reporter: Damitha Kumarage
> Assignee: Dinesh Premalal
> Fix For: 1.3.1
>
>
> In the following code of axis2_op_register_op_ctx() function
> msg_id = axis2_msg_ctx_get_msg_id(msg_ctx, env);
> if (!msg_id)
> {
> AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
> "Message id not found for message context while "\
> "registering operation context for operation %s", opname);
> return AXIS2_FAILURE;
> }
> When message id is not found in the messages context it is correctly logged as error and returned failure. However every places from which this function called, status is not handled and although error is logged and failure returned still code work successfully. This is behaviour is not acceptable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Assigned: (AXIS2C-1086) In function
axis2_op_register_op_ctx() failure is logged and returned in a working
path.
Posted by "Dinesh Premalal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Premalal reassigned AXIS2C-1086:
---------------------------------------
Assignee: Dinesh Premalal
> In function axis2_op_register_op_ctx() failure is logged and returned in a working path.
> ----------------------------------------------------------------------------------------
>
> Key: AXIS2C-1086
> URL: https://issues.apache.org/jira/browse/AXIS2C-1086
> Project: Axis2-C
> Issue Type: Bug
> Reporter: Damitha Kumarage
> Assignee: Dinesh Premalal
>
> In the following code of axis2_op_register_op_ctx() function
> msg_id = axis2_msg_ctx_get_msg_id(msg_ctx, env);
> if (!msg_id)
> {
> AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
> "Message id not found for message context while "\
> "registering operation context for operation %s", opname);
> return AXIS2_FAILURE;
> }
> When message id is not found in the messages context it is correctly logged as error and returned failure. However every places from which this function called, status is not handled and although error is logged and failure returned still code work successfully. This is behaviour is not acceptable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org