[
https://issues.jboss.org/browse/JBESB-3796?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3796:
------------------------------------------------
Suz <sdorfiel(a)redhat.com> made a comment on [bug
820031|https://bugzilla.redhat.com/show_bug.cgi?id=820031]
Technical note added. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
New Contents:
Exception handling issues can arise after the SyncServiceInvoker fails. If an exception is
thrown after the SyncServiceInvoker call, the error is not sent to the client. This can be
resolved by setting a "FaultTo" EPR in a custom composer-class set on the
service's FS-Provider.
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