My use case applies the concept of atomic document reviewing.
A group of people gets assigned to a reviewing task of a document. The next task can only be done when all people have reviewed the code.
The problem is that according to the document type, the peoples that might be interested in reviewing it may vary. That is only known at runtime, meaning that we don't know a priori how many review instances we are going to get. At the end, all instances must end, so the next task can proceed (e.g. giving a verdict).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263128#4263128
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263128
As stated on the workflow patterns website:
anonymous wrote : jBPM does not support this pattern. There is a proposed implementation in Java of a node-type Node to capture this semantics. As the solution relies on java-coding we consider it outside the capabilities of the proposed jPDL language
So basically it means you can do it with jBPM, but it requires some Java coding.
Can you perhaps explain your use case?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263124#4263124
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263124
According to this site jBPM 3.x supports the variant without synchronization:
http://www.workflowpatterns.com/patterns/control/multiple_instance/wcp12.php
Is this also the case for jBPM 4.x? If yes this would be the point to start, no?
http://www.workflowpatterns.com/patterns/control/index.php
Workflow Patterns lists 3 variants of your desired pattern. Take a look at the patterns 13, 14 and 15. Before you can think of an implementation first of all you would have to be sure about what you are trying to achieve.
Basically instead of a task or subprocess being created directly a kind of "controller" would need to be created who creates the number of process or task instances which is needed. It would need to hold a list of all created instances. As soon as an instance has finished the controller would need to be notified. As soon as it has received notifications from all instances in the maintained list the process flow could continue.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263113#4263113
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263113
thx for the links. i still don't know the way this should work..i will try to bild it and make some changes but i don't know whom should i send the changes. I don't see a lot of interest in geting new developers for the project. that is why i asked if you gotta work for jboss to get the commit rights.
as i know the anonymous SVN isn not realy up to date with the source code... is it so?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262960#4262960
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262960
