Solution_ - the solution type, the class with the PlanningSolution annotationpublic class ChainedChangeMove<Solution_> extends ChangeMove<Solution_>
| Modifier and Type | Field and Description |
|---|---|
protected Object |
newTrailingEntity |
protected Object |
oldTrailingEntity |
entity, toPlanningValue, variableDescriptor| Constructor and Description |
|---|
ChainedChangeMove(Object entity,
GenuineVariableDescriptor<Solution_> variableDescriptor,
Object toPlanningValue,
Object oldTrailingEntity,
Object newTrailingEntity) |
ChainedChangeMove(Object entity,
GenuineVariableDescriptor<Solution_> variableDescriptor,
SingletonInverseVariableSupply inverseVariableSupply,
Object toPlanningValue) |
| Modifier and Type | Method and Description |
|---|---|
ChainedChangeMove<Solution_> |
createUndoMove(ScoreDirector<Solution_> scoreDirector)
Called before the move is done, so the move can be evaluated and then be undone
without resulting into a permanent change in the solution.
|
protected void |
doMoveOnGenuineVariables(ScoreDirector<Solution_> scoreDirector)
Like
AbstractMove.doMove(ScoreDirector) but without the ScoreDirector.triggerVariableListeners() call
(because AbstractMove.doMove(ScoreDirector) already does that). |
boolean |
isMoveDoable(ScoreDirector<Solution_> scoreDirector)
Called before a move is evaluated to decide whether the move can be done and evaluated.
|
ChainedChangeMove<Solution_> |
rebase(ScoreDirector<Solution_> destinationScoreDirector)
Rebases a move from an origin
ScoreDirector to another destination ScoreDirector
which is usually on another Thread or JVM. |
equals, getEntity, getPlanningEntities, getPlanningValues, getSimpleMoveTypeDescription, getToPlanningValue, getVariableName, hashCode, toStringdoMove, rebaseArray, rebaseListprotected final Object oldTrailingEntity
protected final Object newTrailingEntity
public ChainedChangeMove(Object entity, GenuineVariableDescriptor<Solution_> variableDescriptor, SingletonInverseVariableSupply inverseVariableSupply, Object toPlanningValue)
public boolean isMoveDoable(ScoreDirector<Solution_> scoreDirector)
MovePlanningSolution.It is recommended to keep this method implementation simple: do not use it in an attempt to satisfy normal hard and soft constraints.
Although you could also filter out non-doable moves in for example the MoveSelector
or MoveListFactory, this is not needed as the Solver will do it for you.
isMoveDoable in interface Move<Solution_>isMoveDoable in class ChangeMove<Solution_>scoreDirector - the ScoreDirector not yet modified by the move.public ChainedChangeMove<Solution_> createUndoMove(ScoreDirector<Solution_> scoreDirector)
AbstractMovecreateUndoMove in class ChangeMove<Solution_>scoreDirector - the ScoreDirector not yet modified by the move.protected void doMoveOnGenuineVariables(ScoreDirector<Solution_> scoreDirector)
AbstractMoveAbstractMove.doMove(ScoreDirector) but without the ScoreDirector.triggerVariableListeners() call
(because AbstractMove.doMove(ScoreDirector) already does that).doMoveOnGenuineVariables in class ChangeMove<Solution_>scoreDirector - never nullpublic ChainedChangeMove<Solution_> rebase(ScoreDirector<Solution_> destinationScoreDirector)
MoveScoreDirector to another destination ScoreDirector
which is usually on another Thread or JVM.
The new move returned by this method translates the entities and problem facts
to the destination PlanningSolution of the destination ScoreDirector,
That destination PlanningSolution is a deep planning clone (or an even deeper clone)
of the origin PlanningSolution that this move has been generated from.
That new move does the exact same change as this move,
resulting in the same PlanningSolution state,
presuming that destination PlanningSolution was in the same state
as the original PlanningSolution to begin with.
Generally speaking, an implementation of this method iterates through every entity and fact instance in this move,
translates each one to the destination ScoreDirector with ScoreDirector.lookUpWorkingObject(Object)
and creates a new move instance of the same move type, using those translated instances.
The destination PlanningSolution can be in a different state than the original PlanningSolution.
So, rebasing can only depend on the identity of planning entities and planning facts,
which is usually declared by a PlanningId on those classes.
It must not depend on the state of the planning variables.
One thread might rebase a move before, amid or after another thread does that same move instance.
This method is thread-safe.
rebase in interface Move<Solution_>rebase in class ChangeMove<Solution_>destinationScoreDirector - never null, the ScoreDirector.getWorkingSolution()
that the new move should change the planning entity instances of.Copyright © 2006–2021 JBoss by Red Hat. All rights reserved.