[esb-issues] [JBoss JIRA] Closed: (JBESB-1313) There is no way to say, what edge to take, when asynchrously executed esb service fails (service action throws an exception)

There is no way to say, what edge to take, when asynchrously executed esb service fails (service action throws an exception) ---------------------------------------------------------------------------------------------------------------------------- Key: JBESB-1313 URL: https://jira.jboss.org/browse/JBESB-1313 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Process flow Affects Versions: 4.2.1 Reporter: Pavel Kadlec Imagine process graph.... I would like to have two edges going from the service node. One edge would mean that the work was done (service did its work correctly, without problems). The other edge would mean, that service action processing pipeline did not finish its work correctly (some action threw ActionProcessingPipeline exception). Can I model this behaviour? If I take a look at EsbActionHandler.java, it seems to me, that jBPM can not be notified, when esb service throws exception, because message field "FaultTo" is never set. If I call esb service asynchronously, jBPM waits for signalCommand with name of the edge to take. But if esb service fails, esb service does not call signalCommand. ActionProcessingPipeline is terminated, I do not have opportunity to send signalCommand with the name of the fault edge...