[dna-issues] [JBoss JIRA] Updated: (DNA-401) Remove SequencingService Dependency on JCR

[Brian Carothers (JIRA)]

     [ https://jira.jboss.org/jira/browse/DNA-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-401:
--------------------------------

    Attachment: DNA-401.patch


Mostly the same as previous patch, but with a few no-longer-relevant comments removed.

The patch:
- Renames SequencerContext to StreamSequencerContext (causing a surprising percentage of the changed lines in the patch)
- Creates a new SequencerContext that replaces the use of JcrExecutionContext for SequencingService
- Adds the concept of a repository source name to ChangedNode and its ilk to reflect the fact that DNA can manage multiple independent repositories
- Modifies all of the code in SequencingService and StreamSequencerAdapter that used to use the JCR layer for data access to use the graph layer directly.
- Modifies DnaEngine to tie the RepositoryService (actually, the RepositoryLibrary) into the SequencingService so that the sequencing service can determine which repository source the changed node is in and act on that repository source accordingly

The patch breaks one existing test case in StreamSequencerAdapterTest that can't/shouldn't be fixed until ObservationService is modified to not use JCR.  The patch also breaks 4 test cases in the sequencing quickstart.  This test really just needs to get rewritten to use DnaEngine and JcrEngine after ObservationService is changed.  If we adopt this patch, I will make a note in the extant defect for re-writing the quickstarts to use DnaEngine and JcrEngine.

> Remove SequencingService Dependency on JCR
> ------------------------------------------
>
>                 Key: DNA-401
>                 URL: https://jira.jboss.org/jira/browse/DNA-401
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Sequencers
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-401.patch, scratch.patch
>
>
> DNA currently has a circular dependency, in that the JCR project depends on the repository and graph projects (and others) as the backing store while the repository project depends on the existence of a JCR layer for the SequencingService and ObservationService.  Removing the JCR dependency is tentatively planned for the ObservationService as part of DNA-252.  It would be useful to remove the final piece of the circular dependency and make the SequencingService interact directly with the graph layer.
> As I see it, this would have the following benefits:
> 1. Removing a circular dependency in the architecture
> 2. (Ever so slightly) increasing performance by removing the expense of converting DNA nodes and properties to and from their JCR equivalents

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira