Is there a way to access process variables within the timer code of a wait state node? I'm not getting anything else than null values there. Even if I assign a value to my variable in the same timer section it is null again in the next iteration... also if I'm accessing it through context.getVariable("varname"). The same applies to globals... Does anybody know any kind of way of passing data between timers and the rest of the process? -- View this message in context:

Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

That timer properties can not be changed dynamically is one thing. The other thing is that in the code that is executed each time a wait state timer fires, you seem to have no access to any process variables. Would you agree on this, Kris? If yes, is this planned to change in the future? I guess you could at least implement a wait state that continues after a variable delay if you could access variables in the timer code. Namely by updating some fact in the working memory i.e. influence the rule constraint of the wait state. I also tried signalling an event from within the wait state timer and update the working memory from a subsequent action node where I do have access to process variables. This although didn't work with me because of a strange NullPointerException... In case anyone is interested: Here is a small project with three approaches for a wait state node that continues after a variable delay. Neither of them works, but maybe someone can fix that... Reto

demo.variableTimer.zip -- View this message in context:

Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Kris, Thanks a lot! It's true that I do have access to process variables if I assign them already when I'm starting the process (passing the value as a parameter of the startProcess() method). In my first code sample above, I assigned the timer variable only in an OnEntry action of the wait state node, which had no effect... (Maybe this is only true for version 5.0 (?)) But anyway my timer with a variable delay still doesn't work as I expected: The process stays in the wait state until my application terminates, although the constraint condition is met after 3 seconds (I print it out each time the timer fires). So it looks as if the constraint condition is not continuously evaluated... although I'm calling context.getProcessInstance().getWorkingMemory().fireAllRules() after every update... do you see a reason for that in this updated small code sample? http://drools-java-rules-engine.46999.n3.nabble.com/file/n996108/demo.var... demo.variableTimer.v2.zip It's interesting that if I don't insert the timer variable into the working memory, the timer even continues firing after my application terminated (since the constraint is never true and the process stays in the wait state)... So inserting it does have some kind of effect on the evaluation of the constraint, simply not immediately. Reto -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/how-to-access-process... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users