Bug 217978 - [remotesvcs] Discovery may be configurable via OSGi configuration admin service
Summary: [remotesvcs] Discovery may be configurable via OSGi configuration admin service
Status: NEW
Alias: None
Product: ECF
Classification: RT
Component: ecf.discovery (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.2.0   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 211445
  Show dependency tree
 
Reported: 2008-02-06 06:15 EST by Markus Kuppe CLA
Modified: 2010-05-18 21:48 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Kuppe CLA 2008-02-06 06:15:42 EST 
As we've already discussed in [3] org.eclipse.ecf.provider.discovery may be configurable via the OSGi configuration admin [1] and may provide its configuration as OSGi metadata [2].

Possible configuration options:
- activate/deactivate specific discovery providers (e.g. jSLP and JMDNS/Zeroconf)
- activate/deactivate ECF early startup (either on each provider or for the CompositeProvider)
- turn SingletonDiscoveryContainer on/off

Implementation ideas:
org.eclipse.ecf.provider.discovery.CompositeDiscoveryContainerInstantiator
org.eclipse.ecf.provider.discovery.SingletonDiscoveryContainer

[1] OSGi compendium R4, p.65ff
[2] OSGi compendium R4, p.111ff
[3] http://dev.eclipse.org/mhonarc/lists/ecf-dev/msg01323.html
Comment 1 Scott Lewis CLA 2009-05-28 19:14:50 EDT 
Setting target milestone to 3.1.0
Comment 2 Scott Lewis CLA 2009-09-28 19:02:18 EDT 
removing plan and setting target to 3.2