[ https://issues.apache.org/jira/browse/SLING-12848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Sedding resolved SLING-12848. ------------------------------------ Resolution: Fixed > Introduce ContentRepository Registration > ---------------------------------------- > > Key: SLING-12848 > URL: https://issues.apache.org/jira/browse/SLING-12848 > Project: Sling > Issue Type: Improvement > Reporter: Herman Ciechanowiec > Assignee: Herman Ciechanowiec > Priority: Major > Fix For: JCR Oak Server 1.4.4 > > > 1. Jackrabbit Oak has internal dependencies on the > `org.apache.jackrabbit.oak.api.ContentRepository` service. For instance, the > registration of > `org.apache.jackrabbit.oak.spi.security.authentication.external.impl.jmx.SynchronizationMBean` > as a JMX MBean will not occur if a `ContentRepository` service is > unavailable > ([https://github.com/apache/jackrabbit-oak/blob/b5c317af752b3c421c9d341a7cfca407dff29af5/oak-auth-external/src/main/java/org/apache/jackrabbit/oak/spi/security/authentication/external/impl/ExternalLoginModuleFactory.java#L203-L206]). > 2. A standard Apache Sling application based on the Apache Sling Starter does > not register a `ContentRepository` service, and no such logic is implemented > in any of the Apache Sling bundles. Therefore, code that is dependent on the > existence of a registered `ContentRepository` service does not work as > expected. Among other things, the registration of a `SynchronizationMBean` as > a JMX MBean does not happen. > 3. The proposed solution is to introduce the `ContentRepository` registration > in the `sling-org-apache-sling-jcr-oak-server` bundle, which is responsible > for repository initialization. This solution was agreed upon in this email > thread: [https://lists.apache.org/thread/xt4r7zo7gr4z0ppymp9flfcyvfj6yg97]. -- This message was sent by Atlassian Jira (v8.20.10#820010)