Hi,

We received some time ago a bug report that JMX MBeans are not
registered when running the Sling Starter [1].

We narrowed it down to the platform MBean server not being registered
as an OSGi service [2].

I think this used to work because the startupmanager bundle was
included in the Sling Launchpad [3]. But now we don't include it
because it's launchpad-specific and also is tied to the launchpad.api
bundle.

I think this is good functionality to have and would like to add it
back. I see three options:

1. We add the launchpad stuff back. I don't like this because it it
would bring in too much baggage to the Starter.

2. We create a new bundle, which should be really small and self-
contained. Not the end of the world, but it's one more bundle.

3. We find a good place for this in an existing bundle.

My personal preference would be 3 > 2 > 1.

Thoughts? Does anyone have an idea for an existing bundle to use for
this functionality?

Thanks,
Robert

[1]: https://issues.apache.org/jira/browse/SLING-12367
[2]:
https://github.com/apache/sling-org-apache-sling-jcr-oak-server/pull/11#issuecomment-2480427031
[3]:
https://github.com/apache/sling-org-apache-sling-launchpad-startupmanager/blob/76cb5e2380a6619db685e769175a98a98c94a8f7/src/main/java/org/apache/sling/launchpad/startupmanager/Activator.java#L47

Reply via email to