Reto, State nodes only support rule constraints. The reason is that a constraint in a wait state should be continuously evaluated (while the state is active), and the only way to do that efficiently is to use a rule for that (as that is basically what a rules engine is good at).
I know the docs on the state node are outdated, will be updating this in the next few days, as this was updated as one of the new 5.1 features. For some simple examples, you can currently check out the junit tests though: http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/integrationtests/ProcessStateTest.java Kris Quoting retoy <reto.lampre...@allianz-suisse.ch>: > > Can anyone tell me what's wrong with this wait state constraint? > System.currentTimeMillis() >= (startWait + 3000) > The exception I'm getting ist: > [5,33]: [ERR 102] Line 5:33 mismatched input '>=' expecting 'then' in > rule > "RuleFlow-Milestone-drools.test.timer-6" > but I don't think that is really getting to the heart of the > problem... > -- > View this message in context: > http://drools-java-rules-engine.46999.n3.nabble.com/Wait-state-constriant-tp986768p986768.html > Sent from the Drools - User mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > rules-users@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
