[
https://issues.apache.org/jira/browse/CXF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483858#comment-13483858
]
Freeman Fang commented on CXF-4600:
-----------------------------------
Aki's suggestion should work, but the root problem is that CXF currently not
exactly follow the JAXWS 3.7 chapter when use java first way for exception
class marshal/unmarshall, mainly not map each getter in the exception and its
superclasses
There's already related discussion[1]&[2] recently, and also a jira ticket[3]
for it
[1]http://cxf.547215.n5.nabble.com/Incompatible-fault-type-is-generated-in-the-wsdl-with-RI-command-td5716852.html
[2]http://cxf.547215.n5.nabble.com/Webfault-td5716784.html
[3]https://issues.apache.org/jira/browse/CXF-4594
Freeman
> Exception inheritance not working over SOAP protocol
> ----------------------------------------------------
>
> Key: CXF-4600
> URL: https://issues.apache.org/jira/browse/CXF-4600
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.4.10, 2.5.6, 2.6.3, 2.7.0
> Reporter: Richard Opalka
> Fix For: 2.4.11, 2.5.7, 2.6.4, 2.7.1
>
> Attachments: CXF-4600-reproducer.zip
>
>
> If method parameter or return type are subject to object inheritance,
> passing such complex classes works without any problems over SOAP.
> But when exception is subject to object inheritance, the inheritance
> is unfunctional over SOAP protocol.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
