Uploaded image for project: 'ModeShape'
  1. ModeShape
  2. MODE-1187

Support non-UUID identifiers

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Blocker
    • 3.0.0.Alpha1
    • 2.5.0.Final
    • Graph (2.x), JCR, Storage
    • None
    • High

    Description

      ModeShape started out implementing JCR 1.0, which required the use of UUIDs for identifiers. Although JCR 2.0 has opened the type of identifiers to be any string, ModeShape doesn't fully support using any strings as identifiers. Therefore, ModeShape should fully support using connectors that use string identifiers (without sacrificing the ability and efficiency of using UUIDs).

      Attachments

        Issue Links

          is incorporated by

          Feature Request - Feature requests from customers and/or users MODE-1289 JCR layer should use Infinispan for caching and storage

          • 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.
          • Closed
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-1186 Make the map-based connector generic to work with non-UUID keys

          • 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.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users MODE-1188 Support connectors to systems that contain their own versioning capabilities

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              rhauch Randall Hauch (Inactive)
              rhauch Randall Hauch (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: