In 6.0.0.CR5 (and earlier) there was a bug in the CH with nullable
variables that forced them to pick a non-null value.
Try 6.0.0.Final. The release announcement will go out next week.
Also, that version has an example (and therefor an integration test) of
a nullable variable:
the hospital bed planning example has been redefined and rewritten to
accommodate for overconstrained planning.
On 21-11-13 05:35, newbie wrote:
I am using 6.0.0CR5. I configure the planning variable to be null.
Now using
the construction heuristic <constructionHeuristic>
<constructionHeuristicType>FIRST_FIT</constructionHeuristicType>
<forager>
<pickEarlyType>FIRST_NON_DETERIORATING_SCORE</pickEarlyType>
</forager>
</constructionHeuristic>
all the planning entities was assigned with a planning variable even if the
assignment lead to a negative hard constraint. I assumed that some of it
will be assigned by null to avoid the negative hard constraint. Is my
assumption correct way of using the nullable planning varibale config?
Thanks.
--
View this message in context:
http://drools.46999.n3.nabble.com/Nullable-Planning-Variable-tp4026757p40...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users