[
https://jira.jboss.org/browse/JBPM-2534?page=com.atlassian.jira.plugin.sy...
]
Maciej Swiderski commented on JBPM-2534:
----------------------------------------
Signaling is implemented in BPMC 2.1 version that will be included in 4.4 release.
Signaling was enabled according to suggestion (execution is active and is of state type).
Worth investigating if custom activity shall be included if they in wait state.
Examples needs to be re-enabled in demo. Will take care of that this week.
add signalling action to console
--------------------------------
Key: JBPM-2534
URL:
https://jira.jboss.org/browse/JBPM-2534
Project: jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Tom Baeyens
Assignee: Maciej Swiderski
Fix For: jBPM 4.4
signalling capabilities need to be added to the console so that all examples become
executable. now there are a couple excluded from deployment.
in case of a state activity, offering the signal action is obvious.
but we still need to work out in which other situations we offer signalling. if that is
not clear, then we could just stick with offering the signal action for all executions for
which condition (execution.isActive() &&
"state".equals(execution.getActivity().getType()) resolves to true
re-enabling the examples in the demo deployment is considered part of this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira