[rules-users] Using "matches" in Guided Rule Editor (BRL)

[Andrea H.]

Dear all,
I have a problem when using the operator "matches" in the Guided Rule
Editor. 
I can use the operator from the drop down list, but when saving the rule,
the tabs "BRL Source" and "Generated DRL" show me that the operator has not
been used at all. Instead, the "operator" tag is left out completely in the
BRL source. 
If I choose a different operator, e.g. "is equal to", save, and switch back
to "matches" (and save again), than the BRL source still shows the operator
"==".
If I however edit the BRL source itself to contain "matches", the rule works
fine in my application.
Strange enough, if I use "and matches" in a multi-part-condition on one
attribute, there does not seem to be this problem (the BRL says "&&
matches"). It seems to be only a problem if the "matches" operator comes in
the first assertion line for an attribute.
I would be really grateful if anyone had an idea on this behaviour, since I
seem to be quite lost! 
Thanks in advance,
Andrea
-- 
View this message in context: http://www.nabble.com/Using-%22matches%22-in-Guided-Rule-Editor-%28BRL%29-tp22438549p22438549.html
Sent from the drools - user mailing list archive at Nabble.com.