Difference between revisions of "OSGi Remote Services and ECF"

From Eclipsepedia

Jump to: navigation, search
(New page: ==Introduction== ECF's support for OSGi 4.2 Remote Services is a layered set of application programming interfaces (APIs). The API layering and the associated modularity (coming from the...)
 
(Introduction)
Line 1: Line 1:
 
==Introduction==
 
==Introduction==
  
ECF's support for OSGi 4.2 Remote Services is a layered set of application programming interfaces (APIs).  The API layering and the associated modularity (coming from the use of OSGi and modular design principles) allows service creators to decide which mechanisms are appropriate for their service, and only use those mechanisms.  This reduces the complexity of creating, deploying, and using remote services in service-oriented architectures, while at the same time giving high flexibility about how integration and interoperability can be accomplished.
+
ECF's support for OSGi 4.2 Remote Services standard is a layered set of application programming interfaces (APIs).  This modular structure (coming from the use of OSGi and modular design principles) allows service creators to decide (at runtime if necessary) which mechanisms and underlying protocols are appropriate for their remote service, and then use only mechanisms.   
 +
 
 +
This approach benefits the service creator in two major ways:  1) it reduces the complexity of creating, deploying, managing, and using remote services...by only using the mechanisms that are actually needed; and 2) giving flexibility to meet any needs for integration and interoperability.  In other words, system complexity is reduced by using only the modules needed for the service, while flexibility is increased.
  
 
Here is a diagram showing the relationship between the various layered APIs in ECF's support of OSGi Remote Services.  APIs are shown in white and gray, implementation/providers are shown in blue.
 
Here is a diagram showing the relationship between the various layered APIs in ECF's support of OSGi Remote Services.  APIs are shown in white and gray, implementation/providers are shown in blue.

Revision as of 16:00, 21 January 2010

Introduction

ECF's support for OSGi 4.2 Remote Services standard is a layered set of application programming interfaces (APIs). This modular structure (coming from the use of OSGi and modular design principles) allows service creators to decide (at runtime if necessary) which mechanisms and underlying protocols are appropriate for their remote service, and then use only mechanisms.

This approach benefits the service creator in two major ways: 1) it reduces the complexity of creating, deploying, managing, and using remote services...by only using the mechanisms that are actually needed; and 2) giving flexibility to meet any needs for integration and interoperability. In other words, system complexity is reduced by using only the modules needed for the service, while flexibility is increased.

Here is a diagram showing the relationship between the various layered APIs in ECF's support of OSGi Remote Services. APIs are shown in white and gray, implementation/providers are shown in blue.

Distributedosgi1.png

Here are two pages (with source) showing the use of ECF's remote services to expose and access a 'hello world' remote service.

  1. RFC119 - Getting Started with ECF's RFC119 Implementation
  2. Remote Services API - Getting Started with Using the ECF Remote Services API

Related Documentation

ECF API Docs

API Javadocs

Getting Started with ECF's RFC119 Implementation

Getting Started with Using the ECF Remote Services API

Distributed EventAdmin Service

Eclipse Communication Framework
API
API DocumentationJavadocProvidersECF/Bot Framework
Development
Development GuidelinesIntegrators Guide