[
http://opencast.jira.com/browse/MH-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26475#comment-26475
]
Josh Holtzman commented on MH-7696:
-----------------------------------
The only approach I can imagine is to inspect the currently installed OSGI
bundles and the components they provide. We can poll the OSGI runtime for a
list of bundles, and report the number of active vs. non-active bundles (though
bundle fragments are never 'active'), so that gets us partially to your goal.
The problem is that we can not get the list of active vs. non-active
"components" that have been registered via declarative services. This is
because the OSGI spec defines no management API for declarative services.
Felix provides such an API, but to date we have been careful not to bind
Matterhorn too tightly to container specific APIs. Where we have, it's been at
the periphery where these features could be replaced (e.g. Felix Fileinstall
and WebConsole). Therefore the best approach is probably to extend the
webconsole to provide a json feed detailing the active vs. starting vs. failed
OSGI bundles and components.
> When has matterhorn loaded successfully?
> ----------------------------------------
>
> Key: MH-7696
> URL: http://opencast.jira.com/browse/MH-7696
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Architecture & Services
> Affects Versions: 1.1
> Reporter: Christopher Brooks
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
