[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-121) Support per-token variables in jBPM

[Ronald van Kuijk (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-121?page=comments#action_12349540 ] 
            
Ronald van Kuijk commented on JBSEAM-121:
-----------------------------------------

I have not used this much in real life jbpm usage. I did use variables per task, which are in fact a copy of the values they had on the process level when the task was created. This sometimes leads to unexpected (unwanted?) behaviour, since e.g. with parallel tasks, the process level variables might have been updated without a (or any) user knowing this. A mechanism like a warning that the values have changed since the task was created might be an option. This is imo however a jbpm issue

> Support per-token variables in jBPM
> -----------------------------------
>
>                 Key: JBSEAM-121
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-121
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: BPM
>            Reporter: Gavin King
>         Assigned To: Gavin King
>
> jBPM variables can be scoped to the entire process instance, or to a single path of execution (Token). Currently Seam does not support the second kind of variable. This is not sufficient. Do we need a new PROCESS_PATH context?? Even this may not be enough in theory, since jBPM actually supports a kind of Token hierarchy. Is there some other solution?

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira