[ https://jira.jboss.org/jira/browse/JBPM-2413?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2413: ------------------------------ Description: 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

[ https://jira.jboss.org/jira/browse/JBPM-2413?page=com.atlassian.jira.plug... ] Ronald van Kuijk updated JBPM-2413: ----------------------------------- Component/s: GPD Runtime Engine -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2413?page=com.atlassian.jira.plug... ] Joram Barrez commented on JBPM-2413: ------------------------------------ The relaton is there because, according to Tom, the foreach can be implemented under the hood in the same manner as the group activity. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2413?page=com.atlassian.jira.plug... ] Sebastian Schneider commented on JBPM-2413: ------------------------------------------- After reading the group activity description in the developer documentation I do not see the connection either. http://docs.jboss.com/jbpm/v4/devguide/html_single/#groupconcurrency A group activity is a kind of sub process for me which has a static definition just like a normal process. Of course there can be concurrent executions within a group activity if the group activity is modelled like this. So you have 2, 3 or more concurrent executions but just as many as you modelled during design time. In contrast the foreach activity could have several concurrent executions. How many exactly would be decided kind of dynamically - maybe even at runtime, right? Or you could define and set a property for the group activity at design time telling the number of concurrent executions which should be created. is the later one in the manner you think of, Tom? -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2413?page=com.atlassian.jira.plug... ] Joram Barrez commented on JBPM-2413: ------------------------------------ The GroupConcurrencyTest is not 100% functionally correct. Every end activity will trigger the continuation of the subprocess, even when multiple parallel paths exist. -- 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

[ 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. -- 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