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
Thanks for the reply.
Just for the records: Chapter 3.5 of the Drools Flow User Guide says that
there are two kinds of constraints: (a) code constraints and (b) rule
constraints, where "code constraints are boolean expressions".
So wait states obviously don't support code constraints... correct
The line "System...3000)" isn't a constraint - it is a boolean expression.
Whether it is correct or not depends on its surroundings.
Syntax aside, note that using a method call that's not time-invariant
is unlikely to produce correct results.
-W
On 22 July 2010 13:31, retoy wrote:
>
> Can anyon
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 gett
