Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

ECF Conference Call 2.05.2008

Revision as of 05:07, 5 February 2008 by Bugs.eclipse.org.lemmster.de (Talk | contribs) (Discovery API)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Discovery API

Separation of Preferences from Discovery UI

Quote from Markus posting to ecf-dev

Thinking about it, I believe it makes sense to decouple the preference UI from the discovery API via the OSGi configuration manager (CM) service. That way consumers can still benefit from the configuration capability of discovery even if they choose to use a pure OSGi runtime.

In we decide to take this route, we can split the work into creating the CM service for org.eclipse.ecf.provider.discovery and into creating a preference page that bases on CM services (with metatype it could be fairly generic).

Inclusion of jSLP and SLP in Build

serviceaccesshandler - technology.ecf initial contribution

https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2038

r-OSGi

Inclusion of r-OSGI and Provider into ECF Build

Integration with Discovery

Shared Editing

Plan of Action

Back to the top