[ https://issues.apache.org/jira/browse/OAK-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833915#comment-13833915 ]
Bertrand Delacretaz commented on OAK-795: ----------------------------------------- Note that in the meantime we have a working SlingRepository using Oak in the Sling project, at http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/oak-server/ with tests in the sibling it-jackrabbit-oak module. > Osgi init issues > ---------------- > > Key: OAK-795 > URL: https://issues.apache.org/jira/browse/OAK-795 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, mk > Reporter: Alex Parvulescu > Assignee: Jukka Zitting > Fix For: 0.13 > > Attachments: OAK-795-it.patch > > > Currently there are some init issues when running in an OSGi env - there can > be more than one call to Oak#createContentRepository using the same NodeStore. > The overlap can come from having a Sling repo call #createContentRepository > via the JCR class and at the same time have > _org.apache.jackrabbit.mk.osgi.MicroKernelService_ call > #createContentRepository on the same NodeStore from the Activator. > The simplest solution for now is to have the oak-core Activator class ignore > the NodeStore services and leave repo impls like the sling one call > #createContentRepository. -- This message was sent by Atlassian JIRA (v6.1#6144)