[
https://issues.apache.org/jira/browse/KARAF-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402302#comment-15402302
]
Guillaume Nodet commented on KARAF-4633:
----------------------------------------
I'd rather go a bit further.
Imho the whole digraph service and hooks should be lazily registered / loaded.
I'm not aware of anyone actually using regions atm, so I think it's safe to
turn them off by default.
* when the features service is loaded, check to see if there are regions, if
so, load the service and register everything
* else, create the empty digraph, but do not register it nor the hooks /
mbeans, etc...
* if a resolution using regions is about to be applied (or if a region is
manually created), then register everything before applying the output of the
resolution
Thoughts ?
> Allow disabling registration of StandardManageableRegionDigraph
> ---------------------------------------------------------------
>
> Key: KARAF-4633
> URL: https://issues.apache.org/jira/browse/KARAF-4633
> Project: Karaf
> Issue Type: Improvement
> Reporter: Fabian Lange
>
> As part of my activities to reduce karaf footprint, I was wondering what was
> triggering the mbean server infrastructure to come up in karaf.
> I saw that org.apache.karaf.features.internal.osgi.Activator.doStart()
> registers the StandardManageableRegionDigraph.
> As i could not find any internal interaction with that mbean, could we make
> it configurable to not register? That would avoid initializing a lot of mbean
> server stuff.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
