[jira] [Commented] (OAK-2910) oak-jcr bundle should be usable as a standalone bundle

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560409#comment-14560409 ] 

Chetan Mehrotra commented on OAK-2910:
--------------------------------------

[~rombert] In Sling currently the oak-server bundle is embedding oak-jcr[1]. Can we try not doing that and see where it starts failing. I suspect there were following reason in the past when opted for this to get going in OSGi

# JAAS Login issues - Get JAAS login performed was result in classloading issue. With Felix JAAS there are some better options to deal with that. So if thats the case we can look into those
# Dependency on non exported classes of oak-jcr - Ideally any other bundle should be able to just make use of {{org.apache.jackrabbit.oak.jcr.osgi.RepositoryManager}} to configure Oak and not need to build up complete Oak setup via Oak builder in OSGi env. May be some aspects are not easy to configure so need to be looked into. 
# Repository Initializer - We would need a way to express in DS that RepositoryManager does not get activated before all known initilaizers are registered. This was not easy so far but with new '<refname>.cardinality.minimum' support added to SCR as part of RFC 190 (Section 5.10 [2]) (see
FELIX-4391) it might be easy

[1] https://github.com/apache/sling/blob/trunk/bundles/jcr/oak-server/pom.xml
[2] https://github.com/osgi/design/raw/master/rfcs/rfc0190/rfc-0190-Declarative_Services_Enhancements.pdf

> oak-jcr bundle should be usable as a standalone bundle
> ------------------------------------------------------
>
>                 Key: OAK-2910
>                 URL: https://issues.apache.org/jira/browse/OAK-2910
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>              Labels: osgi
>             Fix For: 1.3.1
>
>
> Currently oak-jcr bundle needs to be embedded within some other bundle if the Oak needs to be properly configured in OSGi env. Need to revisit this aspect and see what needs to be done to enable Oak to be properly configured without requiring the oak-jcr bundle to be embedded in the repo



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