Well, if I understand everything correctly, a "Best-solution clone" is needed just to remember/represent that state of the solution. It does not have to do anything anymore, therefor some data should not be copied and/or initialized upon cloning. It might be "not optimal" design that drives me to initializing stuff upon cloning, but anyway I think there might be more scenarios where it is useful to know if the solution object is the working solution or a best solution. Right? Regards, Michiel   ----------------- http://www.codessentials.com - Your essential software, for free! Follow us at http://twitter.com/#!/Codessentials ________________________________ From: Geoffrey De Smet <ge0ffrey.spam(a)gmail.comTo: Rules Users List <rules-users(a)lists.jboss.org&gt; Sent: Thursday, February 28, 2013 8:28 AM Subject: Re: [rules-users] planner: when gets a solution cloned? Op 27-02-13 19:50, Michiel Vermandel schreef: Hi, scenarios: Currently this is right IIRC. But mix in multi-threading for 6.1 or 6.2 and there will be more cases of cloning. clone is intended for a best-solution or a new working-solution? Why would you need to know that? Would it alter your cloning behavior somehow? It's probably hackable through BestSolutionRecaller, but it will give you a hard time when upgrading to 6.0 if you do hack it there. >Thanks >Michiel >  >----------------- >http://www.codessentials.com - Your essential software, for free! >Follow us at http://twitter.com/#!/Codessentials >_______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users