[rules-users] Drools Planner: Planning variable gets assigned value out of valueRange => primitive types problem

[Geoffrey De Smet]

Yes, FROM_PLANNING_ENTITY_PROPERTY works in 5.4.0.Final.
You're suffering from a different problem:

Change your planning variable type from long to Long and default it null.
Planner presumes that a variable == null is uninitialized, but a 
variable == 0 it considers initialized.
As a result, the construction heuristic won't bother to initialize the 
variables that are == 0.
The local search heuristic will change it, but there's no guarantee it 
won't change all of them.

For Planner 6.0, there will be 
@PlanningVariable(uninitializedEntityFilter = ...),
which will make it easy to tell Planner that 0 means uninitialized.

Op 30-11-12 10:00, mr_moe schreef:
> I've now downgraded to Drools 5.4.0.Final, but the planning variable still
> gets assigned the value 0 sometimes.
> Shouldn't ValueRangeType.FROM_PLANNING_ENTITY_PROPERTY work in 5.4?
>
>
>
>
> --
> View this message in context: http://drools.46999.n3.nabble.com/Drools-Planner-Planning-variable-gets-assigned-value-out-of-valueRange-tp4020984p4021034.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>