Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-10368

Drive refResourceCollection and refResourceId abstractions throughout the relationship code

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: OpenIDM 6.0.0
    • Fix Version/s: None
    • Component/s: Module - Relationships
    • Labels:
    • Story Points:
      3

      Description

      With the work of breaking the _ref into _refResourceCollection and _refResourceId, the abstractions in the relationship code  (e.g. EdgeToVertexSignaller and EdgeTemporalConstraintsHandler) should be updated to no longer represent a full vertex path with a single String, but rather with a ResourcePath instance representing the vertex resource collection, and a String identifying the vertex id. 

      The number of conversions between the two formats should be minimized. See consumption of EdgeInternals#getResourceId, EdgeInternals#getResourceContainer and EdgeInternals#getFullResourcePath for details.

        Attachments

          Activity

            People

            • Assignee:
              dhogan Dirk Hogan
              Reporter:
              dhogan Dirk Hogan
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: