Introduce ConstraintOccurrenceTotal and make it easier to extend the ConstraintType and
don't split up positive and negative hard constraints types
---------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-2510
URL:
https://jira.jboss.org/jira/browse/JBRULES-2510
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: 5.1.0.M1
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Fix For: FUTURE
* ConstraintType is now an enum and so it's annoying to add VERY_SOFT etc (you
can't reuse the ConstraintOccurrence implementations).
* ConstraintType should not make a difference between positive and negative hard
constraints
* ConstraintOccurrenceTotal should give domain and api support to understand and enumerate
the total of the rules.
Think about:
* new IntConstraintOccurrenceTotal(int level, String ruleId, boolean positiveOrNegative)
* myIntConstraintOccurrenceTotal.createOcccurence(weight, causes)
* LevelBasedScore (instead of HardAndSoftScore?)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira