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 "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/05/03 18:50:17 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 ]

Bertrand Delacretaz updated OAK-795:
------------------------------------

    Attachment: OAK-795-it.patch

The attached patch adds some tests under oak-it/osgi, including one for the SlingRepository service.

I have @Ignored those tests for now due to this issue, but they pass most of the time if I enable the NodeStore tracker in the oak-core Activator, so once this is fixed they should be useful.
                
> 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
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira