So it turns out that the Timer itself was null for some reason. Maybe because it had already expired? Anyway, I have my timer setup in the task, not the task-node. So it dawned on me that I could probably get the task instance directly from the execution context. Basically I was trying to make it harder that it needed to be. That all worked and I was able to re-assign the task. Just for reference, my process definition follows: <process-definition | xmlns="" name="TimerTest"> | <start-state name="start"> | <task name="StartTimerTest"> | <assignment expression="user(david)"></assignment> | <controller> | <variable name="Name" access="read,write,required"></variable> | </controller> | </task> | <transition name="" to="task1"></transition> | </start-state> | <task-node name="task1"> | <task name="GetAge" duedate="2 business minutes"> | <assignment expression="user(david)"></assignment> | <timer name='escalate' | duedate='2 business minutes'> | <action class='com.lsft.jbpm.action.EscalationActionHandler' /> | </timer> | <controller> | <variable name="Age" access="read,write,required"></variable> | </controller> | </task> | <transition name="" to="end1"></transition> | </task-node> | <end-state name="end1"></end-state> | </process-definition>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3943060#3943060 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3943060 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
