[ http://jira.jboss.com/jira/browse/JBPM-845?page=comments#action_12353786 ] Harald Strack commented on JBPM-845: ------------------------------------ "The solution here is too simple" from last comment refers to http://jira.jboss.com/jira/browse/JBPM-399! I would greatly appreciate to integrate this changes into CVS. Should I ask for a developer account at admin-at-jbpm-dot-org? -- 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

[ http://jira.jboss.com/jira/browse/JBPM-845?page=all ] Harald Strack updated JBPM-845: ------------------------------- Description: Hi, why is there not the same functionality for transient variables as for persistent ones when copying variables from a superprocess to a subprocess (process state)? I have seen this thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70407 The proposed solution as seen in jira http://jira.jboss.com/jira/browse/JBPM-399 is implemented in jbpm 3.1.2 that I am actually using. I think this solution is simple but does not fit for the most common case, that a superprocess calls a common suprocess and the subprocess does not know anything about the superprocess. More specific, there could be different superprocesses with different transient variable names. These superprocesses may call a general subprocess... Using the present solution forces the subprocess to know about all possible variablenames of all possible superprocesses - that's really bad! What we need is varible scoping. What can we do? Is it is not difficult to implement similar code for transient variables as you did for persistent ones. Patch for 3.1.3 and 3.1.4 following... was: Hi, why is there not the same functionality for transient variables as for persistent ones when copying variables from a superprocess to a subprocess (process state)? I have seen this thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70407 The proposed solution as seen in jira http://jira.jboss.com/jira/browse/JBPM-399 is implemented in jbpm 3.1.2 that I am actually using. I think this solution is simple (and buggy: it only works when you also habe some persistent varibale mappings!) but does not fit for the most common case, that a superprocess calls a common suprocess and the subprocess does not know anything about the superprocess. More specific, there could be different superprocesses with different transient variable names. These superprocesses may call a general subprocess... Using the present solution forces the subprocess to know about all possible variablenames of all possible superprocesses - that's really bad! What we need is varible scoping. What can we do? Is it is not difficult to implement similar code for transient variables as you did for persistent ones. Patch for 3.1.3 and 3.1.4 following... -- 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

[ http://jira.jboss.com/jira/browse/JBPM-845?page=comments#action_12356820 ] Tom Baeyens commented on JBPM-845: ---------------------------------- subContextInstance.setTransientVariables(superContextInstance.getTransientVariables()); That line is in the process state since 3.1.2. Does that resolve your requirements as well ? In your proposed solution, there is a lot of overhead in the DB schema and the XML schema. So i prefer the approach that is currently taken: Just transfer *all* the transient variables *allways*. What do you think ? -- 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

[ http://jira.jboss.com/jira/browse/JBPM-845?page=comments#action_12356862 ] Tom Baeyens commented on JBPM-845: ---------------------------------- imo, the xml, db updates and extra complexity are not justified by these requirements. there are other ways to go around this problem in your scenario. 1) design your processes so that they use non-overlapping transient names as input. in that case the current impl works fine. 2) add a custom action on creation of your subprocess that maps the transient variables to what the subprocess expects. -- 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