[
https://jira.jboss.org/jira/browse/JBPM-2413?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2413:
----------------------------------------
Correct Joram, the signal in the group does not contain similar code as the normal join
does. Personally I'd like the foreach as the group is modeled on the other hand, group
is not visible in the GPD, so I'd go for the fork/join combo with extending the fork
with a for-each and var attribute.
productize group activity
-------------------------
Key: JBPM-2413
URL:
https://jira.jboss.org/jira/browse/JBPM-2413
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: GPD, Runtime Engine
Reporter: Tom Baeyens
Fix For: jBPM 4.x
1) distill minimal set of test case scenarios that give good coverage. consider all
sorts of combinations between group activity and:
- timers
- variables
- concurrency
- looping
- automatic activities
- wait states
2) review test scenarios with tom
3) implement test scenarios
4) move group example tests from test-db to examples.
5) move group docs from devguide to userguide
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira