[
https://issues.apache.org/jira/browse/AXIS2C-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519933
]
Manjula Peiris commented on AXIS2C-665:
---------------------------------------
Yes there was a problem handling soap fault when a module is engaged. When
axis2_engine_receive failed due to a failure in a module handler, the
axis2_op_client_two_way_send method does not return the msg_ctx even the
recieved fault envelope is set in the msg_ctx. Please see AXIS2C-640. This is
fixed now in the latest svn.
> "axis2_svc_client_get_last_response_has_fault" return 0 even when there is
> really soap fault returned.
> ------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-665
> URL: https://issues.apache.org/jira/browse/AXIS2C-665
> Project: Axis2-C
> Issue Type: Bug
> Components: core/clientapi
> Affects Versions: 1.0.0
> Environment: Windodw Server 2003, English Version, Microsoft Visual
> C++.net 2005, Intel Petium D CPU 3.0G dual core, 2G memory
> Reporter: Rock Wang
> Priority: Critical
>
> "axis2_svc_client_get_last_response_has_fault" return 0 even when there is
> really soap fault returned.
> I have used "axiom_node_to_string" to print the returned soap body by the
> peer service(which is developed by Java and deployed by JBoss), and it reads:
> <env:Fault
> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/";><faultcode>env:Client</faultcode><faultstring>Cannot
> find child element: String_1</faultstring></env:Fault>
> But "axis2_svc_client_get_last_response_has_fault" really returns 0 on it. :-(
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
