Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
ECF's Architecture for Distributed OSGi
Introduction
Rather than expose a single API for supporting distributed OSGi services, ECF is structured as a layered set of APIs, so as to support as many use cases for distributed systems as possible. So, rather than require that all applications use a single API for all their remoting needs, we allow applications to decide what mechanisms they need for their particular use case.
Here is a diagram to show the relationship between the various components within ECF's implementation of distributed OSGi
At the Top: RFC119
At the top of the stack shown above is the implementation of the two major components of RFC119, discovery and distribution. We have a Getting Started with ECF's RFC119 Implementation that has sample code and shows how to setup, register, and publish a remote service, and how to write a consumer of that remote service using the standard ServiceTracker.
For reference, this top-level is implemented via three small bundles:
org.eclipse.ecf.osgi.services: Implementation of RFC119-defined interface classes (11k).
org.eclipse.ecf.services.osgi.discovery: Implementation of RFC119 discovery based upon the ECF Discovery API. Also includes provisional API to extend and/or customize the behavior of the implementation. See here for the package javadocs (32k).
org.eclipse.ecf.services.osgi.distribution: Implementation of RFC119 distribution based upon the ECF Remote Services API. Also includes provisional API to extend and/or customize the runtime behavior of the implementation. See here for the package javadocs (53k).
One Level Down: ECF Remote Services
Below