Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1.0.Beta1
    • Component/s: engine
    • Labels:
      None
    • Last commented by a user?:
      true
    • Sprint:

      Description

      Is the ConstraintLocation abstraction still helpful or should its information be merged into the ConstrainedElement hierarchy?

      In ValidatorImpl, there are still some references to methods from ConstraintLocation; ideally this shouldn't be the case as the validation routine should only work on the aggregated model, while ConstraintLocation (with properties for physical elements such as getMember() belongs to the raw model.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                gunnar.morling Gunnar Morling
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: