[
https://issues.apache.org/jira/browse/JCR-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838569#comment-13838569
]
Chetan Mehrotra commented on JCR-3705:
--------------------------------------
+1 for making it part of API
bq. (the DataStore API is in jackrabbit-api, but I assume oak depends on that
anyway)
It falls under {{org.apache.jackrabbit.core}} package and is not part of API
module [1]. Having a new component jackrabbit-data would enable moving all the
common stuff like CachingDataStore [2] and MultiDataStore at one place and can
then be used in Oak
[1] https://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-api/
[2]
https://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-aws-ext/src/main/java/org/apache/jackrabbit/aws/ext/ds/CachingDataStore.java
> Extract data store API and implementations from jackrabbit-core
> ---------------------------------------------------------------
>
> Key: JCR-3705
> URL: https://issues.apache.org/jira/browse/JCR-3705
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Jukka Zitting
>
> In Oak we'd like to use the Jackrabbit data stores (OAK-805). Doing so would
> currently require a direct dependency to jackrabbit-core, which is
> troublesome for various reasons.
> Since the DataStore interface and its implementations are mostly independent
> of the rest of Jackrabbit internals, it should be possible to avoid that
> dependency by moving the data store bits to some other component.
> One alternative would be to place them in jackrabbit-jcr-commons, another to
> create a separate new jackrabbit-data component for this purpose. WDYT?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
