[
https://issues.jboss.org/browse/JBESB-3830?page=com.atlassian.jira.plugin...
]
Tom Cunningham commented on JBESB-3830:
---------------------------------------
From Martin Weiler:
The reason I raised this question was to avoid ending up with the same situation as with
the SignalCommand of the old jBPM3 BpmProcessor, which was removed in ESB 4.5 (SOA-P 5.0)
by JBESB-2315. Some citations from the forum:
https://community.jboss.org/thread/144559:
The SignalCommand is no longer available, [...] because it is not safe to use it
without additional information. Any service invocation from jBPM to ESB and back stores
the appropriate information within the EPR and is automatically handled. All the ESB
service has to do is respond to the correct EPR.
https://community.jboss.org/thread/153723:
direct use of the signal command within jBPM 3 will fail very quickly once you move
away from the simple scenarios, which is why we jump through those hoops. [...] The
present integration focusses on interactions between ESB services and jBPM, forcing a
'one time only' execution of the signal. The EPR contains additional information
necessary to enforce that guarantee, i.e. one request and one response.
Add ActionHandler equivalent and correlation checks to jbpm5
integration
------------------------------------------------------------------------
Key: JBESB-3830
URL:
https://issues.jboss.org/browse/JBESB-3830
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.11
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.12
--
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