You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/07/11 09:20:05 UTC

[jira] [Commented] (CAMEL-6526) @Webfault details are not set in transacted routes

    [ https://issues.apache.org/jira/browse/CAMEL-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623284#comment-14623284 ] 

Claus Ibsen commented on CAMEL-6526:
------------------------------------

Ah so somewhere in the cxf consumer it grabs the caused exception and uses that as a soap fault? 

And are you saying that it picks the wrong exception such as RuntimeCamelException instead of the real cause? Yeah sounds like we should grab the deepest child exception.

> @Webfault details are not set in transacted routes
> --------------------------------------------------
>
>                 Key: CAMEL-6526
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6526
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.11.0
>            Reporter: Peter Leibiger
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 2.16.0
>
>
> In a transacted route, checked exceptions are wrapped by a RuntimeCamelException - the CxfConsumer should use the wrapped cause as fault, if it exists.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)