[rules-users] followup - 'or' for different field constraints

Olenin, Vladimir (MOH) Vladimir.Olenin at moh.gov.on.ca
Tue Mar 27 11:01:43 EDT 2007


... the only thing that would not be allowed is to do the binding on the
this 'connective constraint', since it would make sense. Eg, Record
($invalidBinding : fieldAsString matches "[zxc]" or fieldAsInt > 0) ) ,
since it's kind of 'views' for the 'field' variable, while this one will
work: Record ($correctBidning : field, fieldAsString matches "[zxc]" or
fieldAsInt > 0) ), ie you need to bind the 'original' field, NOT the views.
To think of this, it would actually be need to the <field>AsString,
<field>AsInt, etc getters to be autogenerated.... Or even better - do that
behind the scene depending on the context, if there is no ambiguity
involved...

 

Vlad

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20070327/4a3f7076/attachment.html 


More information about the rules-users mailing list