[dna-issues] [JBoss JIRA] Updated: (DNA-401) Remove SequencingService Dependency on JCR
[
https://jira.jboss.org/jira/browse/DNA-401?page=com.atlassian.jira.plugin...
]
Brian Carothers updated DNA-401:
--------------------------------
Attachment: scratch.patch
Patch that addresses the issue but breaks the sequencing quickstart. Unfortunately, that
quick start is heavily dependent on the existence of a JackRabbit repository to support
the existing JCR dependencies in ObservationService and SequencingService. There seems to
be a chicken-or-egg problem with which to fix first.
This patch passes all other tests (save one that depends on ObservationService being
converted and is @Ignored for now), but has not been reviewed to check that relevant
documentation is updated and should not be committed in its current state. Most of the
patch is just churn from renaming SequencerContext to StreamSequencerContext.
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: 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