[
https://issues.apache.org/jira/browse/OAK-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-2909:
----------------------------------
Fix Version/s: (was: 1.3.2)
1.3.3
Bulk move to 1.3.3.
> 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
> Labels: modularization, technical_debt
> Fix For: 1.3.3
>
>
> 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)
