[
https://issues.apache.org/jira/browse/AXIS2C-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761210#action_12761210
]
Damitha Kumarage commented on AXIS2C-1279:
------------------------------------------
When a service return NULL without setting error code(a common mistake that
could happen by service writer) then this fault occur. I have fixed this
perticuler problem by checking for "No Error" in the message receiver. This
could be considered as the 3rd solution to the above problem
> A soap fault of "No Error" return
> ---------------------------------
>
> Key: AXIS2C-1279
> URL: https://issues.apache.org/jira/browse/AXIS2C-1279
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine
> Reporter: Damitha Kumarage
> Fix For: Next Version
>
>
> A soap fault with reason "No Error" return for certain errors at server side.
> The reason is that some times failures happen at server side but error code
> is not set for these. When at later times code see the status failure and
> call axutil_error_get_message() then it give the wrong message "No Error".
> To avoid this there are two solutions
> 1. Whenever there is an error make sure to call set_error_code(). Fix this in
> the current code.
> 2. Avoid using axutil_eror_get_message() function.
> Ideally the solution should be the first one. Two is only a temporary hack.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
