-
Notifications
You must be signed in to change notification settings - Fork 1
Usage
Cohorte Remote Services implements the OSGi Remote Services specification, which interfaces and beans are defined in the OSGi compendium bundle. It is developed as iPOJO components and requires an HTTP service to work.
The required bundles are:
- OSGi Compendium
- iPOJO Core (official project site)
- Felix HTTP Service, or any implementation of the OSGi HTTP Service
- Jabsorb NG (for the Jabsorb-RPC provider)
| Bundle | Description |
|---|---|
| org.cohorte.remote.api | The Cohorte Remote Services API, which contains the specification of providers |
| org.cohorte.remote.utilities | Utility methods for the core implementation and for providers |
| org.cohorte.remote.core | The core implementation, managing providers and registries |
| org.cohorte.remote.dispatcher.servlet | Provides a servlet used for querying content from the export registry |
| org.cohorte.remote.discovery.multicast | The multicast service discovery provider, based on a home-made protocol |
| org.cohorte.remote.jabsorbrpc | The Jabsorb-RPC transport provider, a JSON-RPC protocol with Java types hints |
The org.cohorte.remote.jabsorbrpc bundles requires this Jabsorb fork to work.
The org.cohorte.ecf.provider.jabsorb bundle provides a transport for ECF, compatible with the Jabsorb provider of Cohorte Remote Services and of Pelix Remote Services.
To export a service with Cohorte Remote Services, you just have to add at least of the following property to the service:
| Key | Value |
|---|---|
| service.exported.interfaces |
* or the string array of interfaces to export |
| service.exported.config |
* or the name of a transport provider |
Those properties are defined in the Constant OSGi interface.
Cohorte Remote Services will detect services with those properties and will export them with all transport providers.