You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Marth (JIRA)" <ji...@apache.org> on 2013/11/07 14:49:32 UTC

[jira] [Updated] (OAK-795) Osgi init issues

     [ https://issues.apache.org/jira/browse/OAK-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Marth updated OAK-795:
------------------------------

    Fix Version/s: 0.13

> 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
>             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)