Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-253

Solver configuration must be able to use KieSession defined in kmodule.xml

    XMLWordPrintable

Details

    Description

      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>

      Attachments

        Issue Links

          duplicates

          Feature Request - Feature requests from customers and/or users PLANNER-344 KContainer support: kie-api wrapper for SolverFactory and Solver so Workbench and Execution Server can treat it like a kjar

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is incorporated by

          Story - Used to indicate the smallest unit of work for a team to complete and is end user-facing. Created by Jira Software - do not edit or delete. PLANNER-300 Make OptaPlanner even easier to get started with and use

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Feature Request - Feature requests from customers and/or users PLANNER-504 Expose SolverFactory in the KIE API so it can be loaded from a KieContainer

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          relates to

          Feature Request - Feature requests from customers and/or users PLANNER-288 Multi-tenancy: SolverFactory.buildSolver is slow when <scoreDrl> usage because KieBase is rebuild every time

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open

          Activity

            People

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              lpetrovi@redhat.com Lukáš Petrovický (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: