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 Dürig (JIRA)" <ji...@apache.org> on 2015/10/14 13:36:05 UTC

[jira] [Updated] (OAK-2909) Review and improve Oak and Jcr repository setup

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

Michael Dürig updated OAK-2909:
-------------------------------
    Fix Version/s: 1.4

> Review and improve Oak and Jcr repository setup
> -----------------------------------------------
>
>                 Key: OAK-2909
>                 URL: https://issues.apache.org/jira/browse/OAK-2909
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, jcr
>            Reporter: Michael Dürig
>            Assignee: Francesco Mari
>              Labels: modularization, technical_debt
>             Fix For: 1.4
>
>
> There is the {{Oak}} and {{Jcr}} builder classes for setting up Oak and Jcr repositories. Both builders don't have clear semantics regarding the life cycle of the individual components they register. On top of that the requirements regarding those life cycles differ depending on whether the individual components run within an OSGi container or not. In the former case the container would already manage the life cycle so the builder should not. 
> IMO we should specify the builders to only be used for non OSGi deployments and have the manage the life cycles of the components they instantiate. OTOH for OSGi deployments we should leverage OSGi subsystems to properly set things up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)