MatchesConstraint and NotMatchesConstraint create inverse verifier rules. ------------------------------------------------------------------------- Key: JBRULES-2512 URL: https://jira.jboss.org/browse/JBRULES-2512 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Esteban Aliverti Assignee: Mark Proctor Priority: Minor When creating a MatchesConstraint for a Field, verifier should fails when the Fails doesn't match the pattern. Right now it is working in the opposite way. Same happens with NotMatchesConstraint. i.e. Here is a part of the verifier rule Generated by NotMatchesConstraint when I defined a Constraint dictating: 'Person's name should not matches "^[A-Z].*$"' $restriction :LiteralRestriction( fieldPath == $field.path, valueAsString not matches "^[A-Z].*$" ) Because I want verifier to fail when the name doesn't matches "^[A-Z].*$", the generated verifier rule should be: valueAsString matches "^[A-Z].*$" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira