[ http://jira.jboss.com/jira/browse/JBPM-10?page=history ]
Tom Baeyens updated JBPM-10:
----------------------------
Description:
the jbpm default join does not synchronize as the pattern 'synchronization'
describes.
the jbpm default join synchronizes based on the brother-and-sister-tokens.
meaning the join takes the parent token of the token that arrives in a join.
then all active the children of that token are considered.
the workflow pattern sync is based on process model information. meaning that
exactly one token has to arrive in the join over each distinct arriving
transition. this implies a set of restrictions on the runtime execution but
that is not the issue.
was:
the jbpm default join does not synchronize as the pattern 'synchronization'
describes.
the jbpm default join synchronizes based on the brother-and-sister-tokens.
meaning the join takes the parent token of the token that arrives in a join.
then all active the children of that token are considered.
the workflow pattern sync is based on process model information. meaning that
exactly one token has to arrive in the join over each distinct arriving
transition. this implies a set of restrictions on the runtime execution but
that is not the issue.
Environment:
Component: Core Engine
> add support for the synchronisation pattern
> -------------------------------------------
>
> Key: JBPM-10
> URL: http://jira.jboss.com/jira/browse/JBPM-10
> Project: JBoss jBPM
> Type: Sub-task
> Components: Core Engine
> Reporter: Tom Baeyens
> Assignee: Tom Baeyens
>
>
> the jbpm default join does not synchronize as the pattern 'synchronization'
> describes.
> the jbpm default join synchronizes based on the brother-and-sister-tokens.
> meaning the join takes the parent token of the token that arrives in a join.
> then all active the children of that token are considered.
> the workflow pattern sync is based on process model information. meaning that
> exactly one token has to arrive in the join over each distinct arriving
> transition. this implies a set of restrictions on the runtime execution but
> that is not the issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
