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

XML file for domain configuration (as an alternative to domain class annotations) to externalize that configuration

    XMLWordPrintable

    Details

      Description

      There is a configuration stuff being specified by annotations on domain entities like @PlanningVariable, @PlanningEntity and so on. This configuration could be all placed in some xml file (referenced from solverConfig.xml) so that user can choose configuration style he likes.

      original use case: comparing several configurations without having duplication of domain entities

      Of course, anything that is exposed in the XML is also exposed in the programmatic Config.java API too.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              rsynek Radovan Synek
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated: