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

Workbench: @PlanningEntityCollectionProperty is used even if the field is a single entity (not a collection)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 6.5.0.Final
    • optaplanner-wb
    • NEW
    • NEW

      I can define a @PlanningSolution.entity : PlanningEntity field in data modeler. I want to annotate the field with @PlanningEntityProperty but I can only see the checkbox labeled "Planning Entity Collection" which obviously adds the @PlanningEntityCollectionProperty. There needs to be a way to add the @PlanningEntityProperty as well.

      In my opinion the best way would be to have a single checkbox with a general label (maybe just "Planning entity") which would add one of the two annotations depending on whether the field type is a collection or not.

              jlocker Jiří Locker (Inactive)
              jlocker Jiří Locker (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: