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

LocationStrategyResolver should support custom immutable classes too

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Minor
    • Future
    • None
    • optaplanner-core
    • NEW
    • NEW

    Description

      Now, immutable classes require a @PlanningId to support locateWorkingObject() and take up Map space (= memory).

      Either detect those custom immutable classes automatically
      or have the user annotate them with an Immutable annotation.

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users PLANNER-491 Partitioned Search

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated: