[ https://issues.jboss.org/browse/JBRULES-3208?page=com.atlassian.jira.plug... ] Lukáš Petrovický updated JBRULES-3208: -------------------------------------- Assignee: Geoffrey De Smet (was: Mark Proctor) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3208?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-3208: ------------------------------------------- BenchmarkerConfig has a method .add... to add xstream aliasses. I use it in the examples too. If that solves your problem, this issue should be changed that I should document that properly in the manual. Note there is a similar looking problem at the end of a benchmark, that I dealt with for 5.3.O-SNAPSHOT (and by Friday probably 5.3.0.CR1). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3208?page=com.atlassian.jira.plug... ] Lukáš Petrovický commented on JBRULES-3208: ------------------------------------------- I just realized - I used XStream's default driver for serializing the Solutions. (I think it was the DomDriver, but I'm not sure.) I see that Benchmark uses a different XStream driver - perhaps that is where the problem lies. That would be one more argument for Planner to provide tools for serializing Solutions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3208?page=com.atlassian.jira.plug... ] Lukáš Petrovický commented on JBRULES-3208: ------------------------------------------- Any suggestions as to how to overcome this short-term, before a proper solution could be implemented? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3208?page=com.atlassian.jira.plug... ] Geoffrey De Smet updated JBRULES-3208: -------------------------------------- Summary: Benchmarker should support custom reading and writing of solutions (it should not enforce 1 specific xstream configuration) (was: Benchmark doesn't allow for de-serializing XMLs with references) Issue Type: Enhancement (was: Bug) Fix Version/s: 5.4.0.Beta1 Description: Title was: Benchmark doesn't allow for de-serializing XMLs with references I have a solution configuration serialized via XStream [1]. When I'm attempting to benchmark [2] my solver with that solution, I get the following error: [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2:java (default-cli) on project tournaments: An exception occured while executing the Java class. null: InvocationTargetException: Problem reading unsolvedSolutionFile: src/main/resources/input-tiny.xml: Invalid reference [ERROR] ---- Debugging information ---- [ERROR] reference : ../../group [ERROR] class : org.drools.planner.examples.tournaments.model.Team [ERROR] required-type : org.drools.planner.examples.tournaments.model.Team [ERROR] converter-type : com.thoughtworks.xstream.converters.reflection.ReflectionConverter [ERROR] line number : 22 [ERROR] class[1] : org.drools.planner.examples.tournaments.TournamentsSolution [ERROR] version : null [ERROR] ------------------------------- I can see two solutions: a) Make it so that Planner benchmark does understand XStream's XML. b) Provide a method inside Planner to serialize Solutions in a way that benchmark will understand them later. References: [1] https://github.com/triceo/Drooling-Tournaments/blob/master/src/main/resou... [2] https://github.com/triceo/Drooling-Tournaments/blob/master/src/main/resou... [3] https://github.com/triceo/Drooling-Tournaments was: I have a solution configuration serialized via XStream [1]. When I'm attempting to benchmark [2] my solver with that solution, I get the following error: [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2:java (default-cli) on project tournaments: An exception occured while executing the Java class. null: InvocationTargetException: Problem reading unsolvedSolutionFile: src/main/resources/input-tiny.xml: Invalid reference [ERROR] ---- Debugging information ---- [ERROR] reference : ../../group [ERROR] class : org.drools.planner.examples.tournaments.model.Team [ERROR] required-type : org.drools.planner.examples.tournaments.model.Team [ERROR] converter-type : com.thoughtworks.xstream.converters.reflection.ReflectionConverter [ERROR] line number : 22 [ERROR] class[1] : org.drools.planner.examples.tournaments.TournamentsSolution [ERROR] version : null [ERROR] ------------------------------- I can see two solutions: a) Make it so that Planner benchmark does understand XStream's XML. b) Provide a method inside Planner to serialize Solutions in a way that benchmark will understand them later. References: [1] https://github.com/triceo/Drooling-Tournaments/blob/master/src/main/resou... [2] https://github.com/triceo/Drooling-Tournaments/blob/master/src/main/resou... [3] https://github.com/triceo/Drooling-Tournaments -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3208?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-3208: ------------------------------------------- My prototype works, I 'll push my changes soon. Then see org.drools.planner.examples.machinereassignment.persistence.MachineReassignmentPlanningProblemIO -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3208?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-3208. --------------------------------------- Resolution: Done Fixed with ProblemIO. See manual. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira