[
https://issues.apache.org/jira/browse/OAK-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562511#comment-14562511
]
Robert Munteanu commented on OAK-2910:
--------------------------------------
I took a look of what it would take to start using the RepositoryManager in
Sling ( not tested yet ). Here's a list of my first findings, based mostly on
the
[OakSlingRepositoryManager|https://github.com/apache/sling/blob/32b05ad492cbaa70fd007fdfd7ae05d6fe4ac0d4/bundles/jcr/oak-server/src/main/java/org/apache/sling/oak/server/OakSlingRepositoryManager.java]
1. I am not sure do to define an {{EditorHook}} which wraps the
{{VersionEditorProvider}}
2. We register a number of {{EditorProvider}} instances. By default these are
all OSGi components so they would all get picked up since they are deployed by
oak-core. Not sure how/if we can do some filtering for them.
{{ConfigurationPolicy.REQUIRE}} is an option, but that would require to
annotate all components.
3. There is no possibility to configure the default workspace name, although
that would be trivial to add.
4. We register a {{NodeAggregator}}, but that does not seem to be (directly)
picked up by the RepositoryManager
5. We register an {{Executor}} service to be used by Oak. Not sure if that is
something which needs to be addressed here, just pointing it out.
6. We need to configure the adminPrincipalName explicitly, not sure if there is
an extension point in Oak which we can use instead of what we do in
[OakSlingRepository#createAdministrativeSession|https://github.com/apache/sling/blob/32b05ad492cbaa70fd007fdfd7ae05d6fe4ac0d4/bundles/jcr/oak-server/src/main/java/org/apache/sling/oak/server/OakSlingRepository.java#L59-L67]
> oak-jcr bundle should be usable as a standalone bundle
> ------------------------------------------------------
>
> Key: OAK-2910
> URL: https://issues.apache.org/jira/browse/OAK-2910
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Labels: osgi, technical_debt
> Fix For: 1.3.1
>
>
> Currently oak-jcr bundle needs to be embedded within some other bundle if the
> Oak needs to be properly configured in OSGi env. Need to revisit this aspect
> and see what needs to be done to enable Oak to be properly configured without
> requiring the oak-jcr bundle to be embedded in the repo
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
