[ https://jira.jboss.org/browse/JBPM-2696?page=com.atlassian.jira.plugin.sy... ] Alejandro Guizar updated JBPM-2696: ----------------------------------- Labels: action jbpm3 node parser timer (was: ) Assignee: Alejandro Guizar Description: When parsing the process definition, timers are read before all events are read. This leads to "create-timer" actions being added to the node-enter events BEFORE your own actions. This doesn't make a lot of sense, normally you want your own actions being executed first and the timer created afterwards. From the engine perspective, it doesn't make any difference (since the timer is started not before the transaction commits), but with that behavior you could e.g. calculate due dates on the node-enter event (before the time is created). This is located in the JpdlXmlReader, method "readNode", these two lines: readNodeTimers(nodeElement, node); readEvents(nodeElement, node); See Forum on the discussion how to solve it. was: When parsing the processdefinition, timers are read before all events are read. This leads to "create-timer" actions being added to the node-enter events BEFORE your own actions. This doesn't make a lot of sense, normally you want your own actions being executed first and the timer created afterwards. From the runtime perspective, it doesn't make any difference (since the timer is started not before the transaciton commits), but with that behavior you could e.g. calculate due dates on the node-enter event (before the time is created). This is located in the JpdlXmlReader, method "readNode", these two lines: readNodeTimers(nodeElement, node); readEvents(nodeElement, node); See Forum on the discussion how to solve it. Complexity: Low Makes sense to me - I will fix in a future release. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira