'eval' is not a field constraint, its a conditional element - it cannot
be nested inside a pattern. You can however use a predicate. predicates
cannot be used where values change over time, 'eval' can.
Mark
jwheeler1 wrote:
I am trying to use the new 3.0.4 feature field constraints. I have
[when]A Policy=status : PolicyStatus()
[when]- expires within {n} days=eo1 : expiresOn\
eval(eo1.compareTo(DateUtils.add(Calendar.DATE, DateUtils.now(), {n}))
<=
0)
I am getting Unexpected token eo1. Michael Neale once said that eval must be
used where things can change over time. I have tried lots of combinations so
am just asking before I keep trying, are evals supported in field
constraints?
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
