[
http://jira.jboss.com/jira/browse/JBRULES-305?page=all ]
Mark Proctor closed JBRULES-305.
--------------------------------
Resolution: Duplicate Issue
This is already fixed here JBRULES-231 for part of 4.0, we will not backport this to
3.0.x
Provide a "not matches" field constraint
----------------------------------------
Key: JBRULES-305
URL:
http://jira.jboss.com/jira/browse/JBRULES-305
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Reteoo
Affects Versions: 3.0.1
Environment: N/A
Reporter: Andy Gerweck
Assigned To: Mark Proctor
JBoss Rules really should have a "not matches" regular expression operator to
complement "matches". There's currently no language construct to directly
support something like this:
rule
when
Email(from matches "me@.*", to !matches "you@.*)
then
doSomething();
end
It's possible to do this using a predicate expression, but JBoss just carried an
article (rightly) condemning Java in rules! We already have negations of all the other
operators (!=/==, </>=, contains/excludes).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira