[ http://jira.jboss.com/jira/browse/JBPM-569?page=comments#action_12353712 ] Arjan van Bentem commented on JBPM-569: --------------------------------------- This might include changing 'deprecated' into 'no longer supported' in lines 1690 and 1691 of jpdl.xml: http://fisheye.jboss.com/browse/JBPM/jbpm.3/jpdl/userguide/en/modules/jpd... 1690 <entry>{content} For backwards compatibility, the condition can also be entered with the 'expression' 1691 attribute, but that attribute is deprecated since 3.2</entry> [ In 2.3.Beta2 'deprecated' seems to imply it is ignored without any warning. When using "Deploy Process Archive" in the Eclipse GPD 3.0.13.1 (as included in the 2.3.Beta2 Suite) then the condition is simply not persisted in JBPM_TRANSITION. This could be a problem of the GPD, but as I assume the GPD simply deploys processdefinition.xml without interpreting it, the attribute is probably ignored somewhere in the jPDL sources. ] It might also include noting that context variables may be accessed using either, for example, #{ quantity > 2 } or #{ contextInstance.variables['quantity'] > 2 } or #{ contextInstance.variables.quantity > 2 } That is: if I understand correctly...! Arjan. -- 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