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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/12/04 16:39:35 UTC
[jira] [Resolved] (OAK-795) Osgi init issues
[ https://issues.apache.org/jira/browse/OAK-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved OAK-795.
-------------------------------
Resolution: Fixed
I fixed the main issue and re-enabled the OSGiIT test case. We no longer have a {{ContentRepository}} service. Instead the JCR layer binds directly to the {{NodeStore}} and other available plugins and uses the {{Oak}} class to wire up the {{ContentRepository}}.
> 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)