[esb-issues] [JBoss JIRA] (JBESB-3796) Exception handling after SyncServiceInvoker fails

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JBESB-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711130#comment-12711130 ] 

RH Bugzilla Integration commented on JBESB-3796:
------------------------------------------------

Jason Shepherd <jshepherd at redhat.com> made a comment on [bug 820031|https://bugzilla.redhat.com/show_bug.cgi?id=820031]

I confirmed this issue still exists on the 5.3 branch. Could we please have this addressed in the next roll-up patch?
                
> Exception handling after SyncServiceInvoker fails
> -------------------------------------------------
>
>                 Key: JBESB-3796
>                 URL: https://issues.jboss.org/browse/JBESB-3796
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.10
>         Environment: SOA Platform 5.2.0
>            Reporter: Jason Shepherd
>         Attachments: SupportCase00634223.zip
>
>
> I have an EBWS based service which is using the SyncServiceInvoker to call a second service. This all works fine but if I throw an exception after the SyncServiceInvoker call the exception is not propagated to the client as a soap fault.
> However if I remove the invocation of the SyncServiceInvoker and throw an exception, a soap fault is sent to the client.
> I have attached a test project which demonstrates this.
> To see the fault just comment out the SyncServiceInvoker call.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira