Bug 269661 - [Contributions] Add ISourceProvider and variable for OSGi services
Summary: [Contributions] Add ISourceProvider and variable for OSGi services
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-23 06:28 EDT by Philipp Kursawe CLA
Modified: 2019-09-06 16:16 EDT (History)
3 users (show)

See Also:


Attachments
Initial implemenation (2.34 KB, text/plain)
2009-03-23 06:30 EDT, Philipp Kursawe CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Kursawe CLA 2009-03-23 06:28:48 EDT
Sometimes I need to know if a certain OSGi service is running and display a UI contribution depending on it. Currently there is no possibility to check for existing OSGi Services in the system.

The idea is to have a new org.eclipse.ui.ISourceProvider for iterating over all OSGi services in the system. This initial implementation provides a new variable "osgi.services" that is iteratable and supports the "equals" core expression for the registered interfaces of a service. 

In a real-world scenario I would like to be able to check if a certain service is started or stopped or only check services that have a specific property set. This would allow UI contributions and enablement be controlled by the state of OSGi services in the system. However I am not sure how you would implement this. Using a PropertyTester maybe? But this would need to know the properties to be tested beforehand, which is not possible with OSGi service properties that are service specific.
Comment 1 Philipp Kursawe CLA 2009-03-23 06:30:30 EDT
Created attachment 129578 [details]
Initial implemenation
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:16:37 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.