jackrabbit.server bundle fails if started before ConfigAdmin

[Bertrand Delacretaz]

Hi,

Currently org.apache.sling.jcr.jackrabbit.server.Activator does this:

    public void start(BundleContext context) throws Exception {
        ....
        ServiceReference sr =
context.getServiceReference(ConfigurationAdmin.class.getName());
        if (sr == null) {
            log.info("Activator: Need ConfigurationAdmin Service to
ensure configuration");
            return;
        }

So if this jackrabbit.server bundle is started before
ConfigurationAdmin, it does not start correctly, yet is shown started
in the OSGi console.

Throwing an Exception instead of log.info would be better already, as
in that case OSGi sees the problem and does not mark the bundle as
started.

There's probably a better way though - how do I tell OSGi that the
jackrabbit.server bundle must be started after the ConfigurationAdmin
service is started?

With SCR I'd add an @scr.reference, but I'm not sure how to do it with
this Activator.

-Bertrand