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.
Difference between revisions of "ECF Conference Call 2.05.2008"
(New page: == Discovery API == === Separation of Preferences from Discovery UI === [http://dev.eclipse.org/mhonarc/lists/ecf-dev/msg01323.html Quote from Markus posting to ecf-dev] Thinking about it...) |
(→Discovery API) |
||
Line 14: | Line 14: | ||
=== Inclusion of jSLP and SLP in Build === | === Inclusion of jSLP and SLP in Build === | ||
+ | |||
+ | === serviceaccesshandler - technology.ecf initial contribution === | ||
+ | https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2038 | ||
== r-OSGi == | == r-OSGi == |
Latest revision as of 05:07, 5 February 2008
Contents
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