[ 
https://issues.apache.org/jira/browse/FELIX-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711567#comment-15711567
 ] 

Alexander Klimetschek commented on FELIX-5410:
----------------------------------------------

I turned this into a standalone plugin, working on it at 
https://github.com/alexkli/osgi-troubleshoot

Under the Apache License. I still would like to contribute this to Apache Felix 
when it's in a good state.

> Web console plugin for troubleshooting wiring issues
> ----------------------------------------------------
>
>                 Key: FELIX-5410
>                 URL: https://issues.apache.org/jira/browse/FELIX-5410
>             Project: Felix
>          Issue Type: New Feature
>          Components: Web Console
>            Reporter: Alexander Klimetschek
>         Attachments: FELIX-5410-with-services.patch, FELIX-5410.patch, 
> webconsole-troubleshoot-services.png, webconsole-troubleshoot.png
>
>
> h4. Feature
> Add a new view/plugin to the standard webconsole that helps to pin point 
> which bundles, services or components are the true source for inactive 
> bundles or services.
> * For *bundles* the underlying assumption would be a healthy system with all 
> bundles active, and thus any inactive can be shown and analyzed as being 
> problematic.
> * For *services/components* one can look at inactive _immediate_ services 
> that fail because of unsatisfied references. For others, the user might need 
> to enter the "problematic" service or component they expect to be running to 
> start the analysis.
> h4. Motivation
> In a larger OSGi application with many bundles and components, it can be 
> difficult to find out the root cause why certain bundles do not start or why 
> a service is not active, especially for folks new to OSGi or with limited 
> knowledge about the application. I have seen many people fail, and thus "not 
> like" OSGi because of such hurdles during development, where it is easy to 
> update on bundle but miss out on crucial dependencies.
> Figuring out is possible through the current web console, but only for 
> experts, if you click through the bundle or service details. This is usually 
> tedious work, if for example a lower level bundle is the problem, and 200 
> others are not active because of it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to