[esb-issues] [JBoss JIRA] (JBESB-3796) Exception handling after SyncServiceInvoker fails
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Fri Oct 12 05:22:03 EDT 2012
[ https://issues.jboss.org/browse/JBESB-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725868#comment-12725868 ]
RH Bugzilla Integration commented on JBESB-3796:
------------------------------------------------
Tadayoshi Sato <tasato at redhat.com> changed the Status of [bug 820031|https://bugzilla.redhat.com/show_bug.cgi?id=820031] from ASSIGNED to MODIFIED
> 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, 4.11
> Environment: SOA Platform 5.2.0
> Reporter: Jason Shepherd
> Assignee: Tadayoshi Sato
> Fix For: 4.11 CP2
>
> Attachments: BZ820031.patch, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list