-
Feature Request
-
Resolution: Done
-
Critical
-
6.1.0.CR1
Currently we support scoring function in the form of DRL, defined as follows:
<scoreDirectorFactory> ... <scoreDrl>some.drl</scoreDrl> </scoreDirectorFactory>
What I would like to be able to do is something like this:
Proposal A) - Rejected in favor of B (see https://github.com/droolsjbpm/optaplanner/pull/82#issuecomment-103377504 for motivation)
<scoreDirectorFactory> ... <scoreKjar>org.foo:bar:1.0</scoreKjar> <!-- Maven GAV --> </scoreDirectorFactory>
This means two things:
- I can either include a kjar from the Business Central.
- Or I can include a kjar from Maven. (Including -SNAPSHOTs.)
Either of the two will allow me to deploy the same solver on different rulebases without recompiling, and to create some distribution mechanisms around the scoring rules.
Proposal B) The solverConfig.xml is a resource of a kjar, so it's part of the KContainer and automatically has access to the KContainer.
Proposal B1)
<scoreDirectorFactory> ... <ksessionName>ksession1</ksessionName> <!-- References a ksession name in kmodule.xml --> </scoreDirectorFactory>
Proposal B2)
<scoreDirectorFactory> ... <kbaseName>kbase1</kbaseName> <!-- References a kbase name in kmodule.xml --> </scoreDirectorFactory>
- duplicates
-
PLANNER-344 KContainer support: kie-api wrapper for SolverFactory and Solver so Workbench and Execution Server can treat it like a kjar
- Resolved
- is incorporated by
-
PLANNER-300 Make OptaPlanner even easier to get started with and use
- Resolved
- is related to
-
PLANNER-504 Expose SolverFactory in the KIE API so it can be loaded from a KieContainer
- Resolved
- relates to
-
PLANNER-288 Multi-tenancy: SolverFactory.buildSolver is slow when <scoreDrl> usage because KieBase is rebuild every time
- Open