[JBoss JIRA] (JBRULES-3334) AbstractTabuAcceptor doesn't add the starting solution as tabu
by Patrik Dufresne (Created) (JIRA)
AbstractTabuAcceptor doesn't add the starting solution as tabu
--------------------------------------------------------------
Key: JBRULES-3334
URL: https://issues.jboss.org/browse/JBRULES-3334
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: 5.3.1.Final
Reporter: Patrik Dufresne
Assignee: Mark Proctor
When setting a complete solution tabu, the starting solution is not considered a Tabu making it possible to visit the same solution again.
Consider a situation where there is construction phase followed by a local search phase. The construction phase will create a solution that will not be added to the tabu list of the local search phased.
To fix it, I suggest to override the function phaseStarted(...) in SolutionTabuAcceptor to add solution to the Tabu map.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBRULES-3448) XLS Decision tables: Add support for Condition column DRL fragments
by Michael Anstis (JIRA)
Michael Anstis created JBRULES-3448:
---------------------------------------
Summary: XLS Decision tables: Add support for Condition column DRL fragments
Key: JBRULES-3448
URL: https://issues.jboss.org/browse/JBRULES-3448
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Michael Anstis
Assignee: Michael Anstis
Fix For: 5.5.0.Beta1
Condition columns in XLS Decision Tables have a row for Object type and a row for code "snippet". The code snippet is taken as predicates within the Object type; for example:-
{code}
CONDITION | CONDITION
----------------------------
MyFact
----------------------------
field1 == | field2 ==
----------------------------
a | b
{code}
This is rather limiting (and certainly not conducive to decision table round-tripping). Ideally we need to support:-
{code}
CONDITION
----------------------------------------------
MyFact( field1 == $param1, field2 == $param2 )
----------------------------------------------
----------------------------------------------
a,b
{code}
Even more ideally it'd be good to be able to register "column handlers" so this can be extended easily.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months