-
Feature Request
-
Resolution: Done
-
Blocker
-
None
-
6.2.0.Final
-
None
-
I propose any work after this point gets a new Jira or else this will never get resolved :)
The Solver Configuration editor should allow to create an solver xml (and modify it later). There are the minimal elements that need to be supported in the prototype:
- 1 solutionClass
- n entityClass
- scoreDirectorFactory
- 1 scoreDefinitionType
- n scoreDrl or n scoreDrlFile
- termination
- secondsSpentLimit
- minutesSpentLimit
- hoursSpentLimit
More fields are welcome too, of course. See the attached design to see how the screen would map to the XML. The XML maps very straigtforwardly to the java beans SolverConfig.java, TerminationConfig.java, etc.
https://github.com/droolsjbpm/optaplanner/blob/master/optaplanner-core/src/main/java/org/optaplanner/core/config/solver/termination/TerminationConfig.java#L41
https://github.com/droolsjbpm/optaplanner/blob/master/optaplanner-core/src/main/java/org/optaplanner/core/config/solver/SolverConfig.java#L45
- causes
-
PLANNER-462 Visual glitch in Solver editor configuration on Firefox
- Resolved
- is blocked by
-
PLANNER-435 Workbench: Data modeler's planning solution should implement Solution interface
- Resolved
-
PLANNER-437 Termination xml: daysSpentLimit and unimprovedDaysSpentLimit support
- Resolved
- is related to
-
PLANNER-325 Workbench: Data modeler support for basic OptaPlanner annotations
- Resolved
-
PLANNER-344 KContainer support: kie-api wrapper for SolverFactory and Solver so Workbench and Execution Server can treat it like a kjar
- Resolved
-
PLANNER-366 Workbench: Construction Heuristics solver configuration
- Resolved
-
PLANNER-367 Workbench: Local Search solver configuration editor (LocalSearchType only)
- Resolved
-
PLANNER-368 Workbench: Termination editor
- Resolved
-
PLANNER-370 Workbench: Exhaustive Search solver editor
- Closed