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

Application properties should support optaplanner.score-drl (Quarkus + Spring)

XMLWordPrintable

    • 2020 Week 49-51 (from Nov 30)
    • 3
    • Undefined
    • NEW
    • NEW

      • Add a field "String constraintsDrl" inOptaPlannerProperties for our Spring starter to allow
        optaplanner.constraints-drl=org/.../timeTableConstraints.drl
      • Similarly for quarkus:
        quarkus.optaplanner.constraints-drl=org/.../timeTableConstraints.drl
      • Look at solver-config-xml for inspiration
      • If it is non empty and the file does not exist, fail fast.
      • If it is empty, and the default "/constraints.drl" exists take that.
      • If it is non-empty or the default "/constraints.drl" exists and a ConstraintProvider exists, fail fast.
      • Update docs chapter "intregation": it has a list of all properties for Spring and Quarkus

      Special:

      • quarkus doesn't support DRL at the moment, because it excludes artifact drools-core-dynamic and depends on drools-core-static, such that CS works in native mode too. We suspect that if a users uses constraints.drl and excludes static and depends on dynamic, DRL will work, in non-native mode only of course. In case that works:
        • If it is non-empty or the default "/constraints.drl" exists, and quarkus is used, and static is in the classpath (or dynamic is not) - maybe use Class.forName() for this detection - then fail fast with a warning that has a second line similar to "Maybe ... exclude drools-core-static and depend on drools-core-dynamic ..."

            rsynek@redhat.com Radovan Synek
            gdesmet@redhat.com Geoffrey De Smet (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: