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

Add support for federating data from external systems

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Blocker
    • 3.1.0.Final
    • 3.0.0.Alpha1
    • Federation, Storage
    • None

    Description

      ModeShape 3 distinguishes between content owned by ModeShape vs content that is in an external system and owned by that external system. All content owned by ModeShape will be stored in ModeShape's internal representation (one or more BSON documents for each node), and this content is merely read from or written to Infinispan (and thus its CacheLoader implementations).

      To talk with external systems, implementing a CacheLoader would likely work, but it might not be very practical. For example, there's no path information in the internal representations, so working with a path-based external system (rather than a key-based one) would be quite a challenge.

      Therefore, ModeShape 3 should define a new SPI that can be easily implemented to read or write nodes, properties and children from/to an external system. It should provide a way to project those external systems into the repository content (preferably configured or defined via content rather than via configuration).

      See the discussion thread for the various options and requirements.

      Attachments

        Issue Links

          blocks

          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

          Feature Request - Feature requests from customers and/or users MODE-1686 Support connectors to systems that contain their own search 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

          Feature Request - Feature requests from customers and/or users MODE-1292 Support accessing file system content

          • 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

          Feature Request - Feature requests from customers and/or users MODE-650 Connector to CMIS

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature Request - Feature requests from customers and/or users MODE-1459 Connect to and use remote ModeShape server

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature Request - Feature requests from customers and/or users MODE-940 Add "observation" support for SVN connector

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

          Feature Request - Feature requests from customers and/or users MODE-1718 Connector to ModeShape

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

          Feature Request - Feature requests from customers and/or users MODE-645 SVN Connector Should Support Native Lock/Unlock

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. MODE-1714 Improve federation paging SPI

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

          Feature Request - Feature requests from customers and/or users MODE-282 Federate content from relational databases

          • 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

          Feature Request - Feature requests from customers and/or users MODE-1712 Allow JCR clients to navigate the nodes exposed by an external source

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

          Feature Request - Feature requests from customers and/or users MODE-1709 New connector to another JCR repository

          • 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

          Feature Request - Feature requests from customers and/or users MODE-1710 Connectors should be able to propagate changes in external systems via events

          • 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

          Feature Request - Feature requests from customers and/or users MODE-1688 All passwords added in 3.1 should be encrypted

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

          Feature Request - Feature requests from customers and/or users MODE-1707 New connector to JDBC metadata

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: