当使用OptaPlanner的SolverManager时，是否需要配置xml或drools drl文件？

Question

public class ConstraintProvider implements 

    org.optaplanner.core.api.score.stream.ConstraintProvider {
        @Override
        public Constraint[] defineConstraints(ConstraintFactory constraintFactory) {
            return new Constraint[]{
                    requiredSkillLevelOfEmployeesForShifts(constraintFactory)
            };
        }

        private Constraint requiredSkillLevelOfEmployeesForShifts(ConstraintFactory constraintFactory) {
            return constraintFactory.from(Shift.class)
                    .groupBy(Shift::getEmployee, sum(Shift::getRequiredSkillLevel))
                    .filter((employee, requiredSkillLevel) -> requiredSkillLevel > employee.getSkillLevel())
                    .penalize("requiredSkillLevelForShifts",
                    HardSoftScore.ONE_HARD,
                    (employee, requiredSkillLevel) -> requiredSkillLevel - employee.getSkillLevel());
        }


    }

    @RestController
    @RequestMapping("/api")
    public class RostersController {

        @Autowired
        private SolverManager<Roster, UUID> solverManager;

        @PostMapping("/solve")
        public Roster solve(@RequestBody Roster problem) {
            UUID problemId = UUID.randomUUID();
            // Submit the problem to start solving
            SolverJob<Roster, UUID> solverJob = solverManager.solve(problemId, problem);
            Roster solution;
            try {
                // Wait until the solving ends
                solution = solverJob.getFinalBestSolution();
            } catch (InterruptedException | ExecutionException e) {
                throw new IllegalStateException("Solving failed.", e);
            }
            return solution;
        }

    }

Answer 1

DRL(scorerules.DRL)和ConstraintProvider是互斥的。您已经开始使用constraintprovider实现约束，所以让我们继续使用它，并在其中添加您可能需要的任何新约束。ConstraintProvider是新的Constraint Streams API的一部分，它允许您在Java中定义约束，并且易于使用ConstraintVerifier进行测试。

<?xml version="1.0" encoding="UTF-8"?>
<solver>
  <solutionClass>com.your.domain.Roster</solutionClass>
  <entityClass>com.your.domain.Shift</entityClass>

  <scoreDirectorFactory>
    <constraintProviderClass>com.your.domain.ConstraintProvider</constraintProviderClass>
  </scoreDirectorFactory>
</solver>