[jboss-jira] [JBoss JIRA] Updated: (JBPM-504) improve sub process variable handling and make variable method names consistent

[Tom Baeyens (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPM-504?page=all ]

Tom Baeyens updated JBPM-504:
-----------------------------

    Fix Version/s:  jBPM jPDL 3.2.1
                       (was: jBPM jPDL 3.2)

i think methods should be added, but no methods should be removed.  to not force people to update their code.

max, we could make the old methods deprecated.

since i don't want the fix for this to remove any methods, (and i want to release 3.2 asap), i moved this item to 3.2.1

> improve sub process variable handling and make variable method names consistent
> -------------------------------------------------------------------------------
>
>                 Key: JBPM-504
>                 URL: http://jira.jboss.com/jira/browse/JBPM-504
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>            Reporter: Tom Baeyens
>         Assigned To: Tom Baeyens
>             Fix For:  jBPM jPDL 3.2.1
>
>
> 1) improve sub process variables:
> maybe a sub process could specify in it's definition what variables are delegated to the super process.  e.g. 
>   <process-definition...>
>     <super-process-variables>
>       <variable name="..." access="..." mapped-name="..." />
>       <variable name="..." access="..." mapped-name="..." />
>       <variable name="..." access="..." mapped-name="..." />
>        ...
>     </super-process-variables>
>     ...
> that would make it easier to write reusable subprocesses.    by default, the variable-lookups could propagate from sub-process to super-process.  
> but for variable creation and variable setting, things are a bit more complicated : you cannot just propagate variable creation to a super process.
> 2) make variable method names more consistent:
> getVariable
> getVariables
> getVariableLocally
> hasVariable
> setVariable
> setVariables
> setVariableLocally
> createVariable should be replaced with setVariableLocally
> addVariables should be replaced with setVariables
> setVariables should be interpreted as a Collections.addAll(): no functionality should be provided for the replacement of the variables map as in a bean-style setter.

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