Amdatu Remote
The Amdatu Remote subproject provides implementations of the OSGi Remote Services 1.0 (OSGi Enterprise R5) and Remote Service Admin 1.1 (OSGi Enterprise R6) specifications. OSGi specifications can be downloaded via the OSGi Alliance homepage.
Project Info
Tools | Location |
|---|---|
Source Code | |
Issue Tracking | |
Continuous Build |
Software Design
Amdatu Remote provides component implementations along the lines of the roles and entities as defined by the Remote Service Admin specification (see Figure 122.1) . Every bundle provides a single discovery, topology manager of remote service admin service implementation. This means different components can be mixed and matched as required ( image source: Figure 122.1; OSGi Enterprise Release 5).
Discovery Components
Discovery components are responsible for publishing exportable as well as discovering importable service endpoints across frameworks. All specification mandated interaction between discovery components and topology manager is based on the exchange of EndpointDescription instances across EndpointListener and EndpointEventListener service interfaces.
HTTP endpoint discovery (Configured)
Bundle | org.amdatu.remote.discovery.configured/0.1.0 | ||||||||||||||
Description | OSGi RSA 1.1 discovery implementation that uses (pre)configured HTTP endpoints that provide the actual service discovery based on HTTP/XML (using the extender format as defined in the RSA specification). | ||||||||||||||
Capability |
| ||||||||||||||
Configuration | The service can both be configured using OSGi environment properties and using Configuration Admin. In case both methods are used the latter takes precedence. The service PID for this service is
|
HTTP endpoint discovery (ZooKeeper)
Bundle | org.amdatu.remote.discovery.zookeeper/unreleased | ||||||||||||||||||
Description | OSGi RSA 1.1 Discovery implementation that uses a ZooKeeper backend to discover HTTP endpoints that provide the actual service discovery based on HTTP/XML (using the extender format). | ||||||||||||||||||
Capability |
| ||||||||||||||||||
Configuration | The service can both be configured using OSGi environment properties and using Configuration Admin. In case both methods are used the latter takes precedence. The service PID for this service is
|