[SLING-2494] JCR Registration should be disabled by default

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: JCR Registration 1.0.0
• Fix Version/s: JCR Registration 1.0.0
• Component/s: JCR
• Assignee: Felix Meschberger
• Reporter: Chetan Mehrotra
• Created: 25/May/12 06:16
• Updated: 07/Mar/14 06:15
• Resolved: 25/May/12 10:07

Description

The current set of JCR registration component RmiRegistrationSupport and JndiRegistrationSupport have Component-> immediate set to true which causes them to activate on default startup. This behavior should be changed to false with activation policy set to ConfigurationPolicy.REQUIRE i.e. should be an opt in activation. For both components the default behavior causes issue

RmiRegistrationSupport - It causes issue in embedding Sling in an AppServer application as the default RMI port is already in use.
JndiRegistrationSupport - The default config refer to org.apache.jackrabbit.core.jndi.provider.DummyInitialContextFactory which is part of Jackrabbit core bundle which is already in OSGi. In my case I need to use com.day.util.jndi.provider.MemoryInitialContextFactory as that is the one present in parent classloader.

Hence in both cases we see exception stacktrace on the first startup and then a user needs to modify the values. For now I am able to workaround that by provide explicit config in packaged war which disables RMI support but it would be helpful if the default behavior is changed