You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2010/01/05 17:00:57 UTC
[jira] Assigned: (CXF-2601) Faults generated with XMLBeans binding
are not wrapped correctly
[ https://issues.apache.org/jira/browse/CXF-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-2601:
--------------------------------
Assignee: Daniel Kulp
> Faults generated with XMLBeans binding are not wrapped correctly
> ----------------------------------------------------------------
>
> Key: CXF-2601
> URL: https://issues.apache.org/jira/browse/CXF-2601
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.2.5
> Environment: Tested on windows with JDK jdk1.5.0_18
> Reporter: Martin Murphy
> Assignee: Daniel Kulp
> Attachments: exceptiontest.zip
>
>
> When Fault in WSDL is defined as simple String and XMLBeans binding is used, then the fault is marshaled in a way, that doesn't allow proper unmarshalling of the Exception on the client side. Example fault looks like
> {code:xml}
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
> <soap:Body>
> <soap:Fault>
> <faultcode>soap:Server</faultcode>
> <faultstring>message</faultstring>
> <detail>detail</detail>
> </soap:Fault>
> </soap:Body>
> </soap:Envelope>
> {code}
> As you can see detail doesn't have any information about fault type. This means that the exception cannot be mapped to the appropriate type
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.