There are currently no examples with multiple planning entity classes, but it is implemented to support multiple. Just configure each of them in the *SolverConfig.xml: <planningEntityClass>org...Entity1</planningEntityClass> <planningEntityClass>org...Entity2</planningEntityClass> ... Op 02-04-12 17:29, TEddahabi schreef: -- With kind regards, Geoffrey De Smet

I forgot about that... The construction heuristics don't support multiple entity classes yet. Feel free to create an issue I plan to do a big refactor & clean up of the construction heuristics code for 5.5.0.Beta1 or Beta2 to make them more configurable, support multiple entity classes and better support multiple variables and huge value ranges. Meanwhile, either hack the existing code to deal with it (pull requests welcome) or instead of using an easy <constructionHeuristic>, write a custom *SolutionInitializer (see examples, some of them still have one). Op 03-04-12 18:20, TEddahabi schreef: -- With kind regards, Geoffrey De Smet

Op 10-04-12 10:44, TEddahabi schreef: Yes, but you need to use 5.4.0.CR1 at least (being released today maybe) and enable ValueRange.excludeUninitializedPlanningEntity = true. Check the CR1 manual on excludeUninitializedPlanningEntity. But this is irrelevant of the construction heuristic problem: you 'll still have 2 entity classes if I understand it correctly, and the <constructionHeuristics> implementations don't support this at this time. Since <localSearch> requires an initialized solution and works much better when combined with a decent construction heuristic, I see no way to avoid a SolutionInitializer to implement a custom construction heuristic. I think you're mixing ValueRangeFromSolutionProperty with ValueRangeFromPlanningEntityProperty. Take a look at the manual to understand the difference between the two. -- With kind regards, Geoffrey De Smet

Why is the error not understandable? Take a look in the manual what excludeUninitializedPlanningEntity does. This won't work on cloudBalance naturally, as no planning value is a planning entity. Op 16-04-12 11:12, TEddahabi schreef: > I use the 5.4.0.CR1 version and make > ValueRange.excludeUninitializedPlanningEntity on true (as you advised me), > but I'm getting this exception : > > at > org.drools.planner.core.domain.variable.AbstractPlanningValueRangeDescriptor.processExcludeUninitializedPlanningEntity(AbstractPlanningValueRangeDescriptor.java:50) > at > org.drools.planner.core.domain.variable.SolutionPropertyPlanningValueRangeDescriptor.processValueRangeAnnotation(SolutionPropertyPlanningValueRangeDescriptor.java:57) > at > org.drools.planner.core.domain.variable.SolutionPropertyPlanningValueRangeDescriptor.<init>(SolutionPropertyPlanningValueRangeDescriptor.java:35) > at > org.drools.planner.core.domain.variable.PlanningVariableDescriptor.buildValueRangeDescriptor(PlanningVariableDescriptor.java:161) > at > org.drools.planner.core.domain.variable.PlanningVariableDescriptor.processValueRangeAnnotation(PlanningVariableDescriptor.java:141) > at > org.drools.planner.core.domain.variable.PlanningVariableDescriptor.processPropertyAnnotations(PlanningVariableDescriptor.java:64) > at > org.drools.planner.core.domain.variable.PlanningVariableDescriptor.processAnnotations(PlanningVariableDescriptor.java:54) > at > org.drools.planner.core.domain.entity.PlanningEntityDescriptor.processPropertyAnnotations(PlanningEntityDescriptor.java:148) > at > org.drools.planner.core.domain.entity.PlanningEntityDescriptor.processAnnotations(PlanningEntityDescriptor.java:64) > at > org.drools.planner.config.solver.SolverConfig.buildSolutionDescriptor(SolverConfig.java:187) > at > org.drools.planner.config.solver.SolverConfig.buildSolver(SolverConfig.java:149) > at > org.drools.planner.config.XmlSolverFactory.buildSolver(XmlSolverFactory.java:112)* > > Could you help me please to fix this problem ? > Thank you !! > > -- > View this message in context: http://drools.46999.n3.nabble.com/Drools-Planner-multiple-planning-entiti... > 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 > -- With kind regards, Geoffrey De Smet

In 5.4.0.CR1, to not have the exception, I put ValueRange.excludeUninitializedPlanningEntity on false (That also works if I dont use this attribute, its default value is false). The solver seems doing the right moves. -- View this message in context: http://drools.46999.n3.nabble.com/Drools-Planner-multiple-planning-entiti... Sent from the Drools: User forum mailing list archive at Nabble.com.