[
https://issues.apache.org/jira/browse/AXIS2C-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1615.
-------------------------------------
Resolution: Won't Fix
Axis2/C uses a native code generator now, see
samples/client/google/google_client.c for workaround.
The AXIOM APIs exist - just requires ~30 lines of boilerplate code.
Axis2/Java does implement full-featured fault handling. However, it would
require significant effort and the Axis2/C focus going forward is JSON.
> The reason in a SOAP fault is never parsed
> ------------------------------------------
>
> Key: AXIS2C-1615
> URL: https://issues.apache.org/jira/browse/AXIS2C-1615
> Project: Axis2-C
> Issue Type: Bug
> Components: wsdl2c tool
> Affects Versions: 1.6.0
> Environment: Debian Squeeze i386
> Reporter: Johan Abbors
> Priority: Critical
> Labels: bug, patch
> Attachments: axis2_codegen_parse_soap_fault_reason.patch
>
>
> I discovered that the faultstring (or reason) in a SOAP fault response never
> gets parsed by the generated code.
> The issue with the deserialize routines for SOAP faults is that the pointer
> "axiom_node_t *soap_detail_node" is not pointing at the correct node, or as I
> my case NULL. Thus the reason is never parsed.
> Even though the pointer should point at the correct node the reason would
> still not be parsed as the deserialize routines are comparing the node names
> incorrectly ("reason" == "faultstring").
> I have attached a patch which solves this problem. The patch is not beautiful
> and should let the ADB fault types deserialize the reason but at least it
> gets the job done.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
