[
https://issues.jboss.org/browse/JBRULES-3557?page=com.atlassian.jira.plug...
]
Geoffrey De Smet commented on JBRULES-3557:
-------------------------------------------
Currently dealt with as such in EntitySelectorConfig:
{code}
if (resolvedCacheType == SelectionCacheType.SOLVER) {
// TODO Solver cached entities are not compatible with DroolsScoreCalculator
// because between phases the entities get cloned and the WorkingMemory
contains those clones afterwards
//
https://issues.jboss.org/browse/JBRULES-3557
throw new IllegalArgumentException("The cacheType (" +
resolvedCacheType
+ ") is not yet supported. Please use PHASE instead.");
}
{code}
Selectors should support cacheType SOLVER with DroolsScoreDirector
too: reuse multi-threading id technology to migrate the selector cache to the new solution
clone
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-3557
URL:
https://issues.jboss.org/browse/JBRULES-3557
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Optional
Selector cacheType solver doesn't work because between phases, the bestSolution is
set as the workingSolution and entities get cloned. Therefor the cached moves are pointing
to the old entities which haven't been inserted into the new Drools Expert working
memory.
--
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