Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Distribution Providers"

(Project Path)
(Dependencies)
Line 49: Line 49:
  
 
====Dependencies====
 
====Dependencies====
<br><br>
+
'''org.eclipse.ecf.provider''':  ECF core bundles, org.eclipse.ecf.sharedobject<br>
org.eclipse.ecf.provider:  ECF core bundles, org.eclipse.ecf.sharedobject<br>
+
'''org.eclipse.ecf.provider.remoteservice''': org.eclipse.ecf.provider, org.eclipse.ecf.remoteservice.asyncproxy
org.eclipse.ecf.provider.remoteservice: org.eclipse.ecf.provider, org.eclipse.ecf.remoteservice.asyncproxy<br>
+
<br>
+
  
 
====Download/Install====
 
====Download/Install====

Revision as of 17:02, 7 October 2015

Introduction

The Remote Services/Remote Service Admin specifications (chaps 100 and 122 in OSGi Enterprise spec) allows for the use of distinct distribution providers for every exported remote service. Distribution providers are responsible for the actual marshalling/serialization and network communication that takes place when a consumer invokes a method on a remote service.

The ECF Architecture allows the use of multiple distribution providers. Further, ECF's open APIs and implementations allows the creation of new distribution providers that may be based upon existing providers or may be created from scratch using any desired transport protocols and/or serialization formats.

Remote Services API

ECF's API for distribution providers is called the Remote Services API. An implementation of this API is the only thing required of distribution provider implementations for them to be successfully used as a standards/compliant implementation of RS/RSA.

Symbolic Name: org.eclipse.ecf.remoteservice
Minimum EE: J2SE-1.5+
Dependencies

Remote Service API Javadoc

All RSA distribution providers implement the Remote Services API.

Distribution Providers

Generic Provider

OSGi Configuration Types/ECF Container Types



ecf.generic.server
ecf.generic.client
ecf.generic.ssl.server
ecf.generic.ssl.client

For example, to export an instance of MyServiceImpl

// Set required OSGi standard service property
props.put("service.exported.interfaces","*");
// Set OSGI standard service.exported.configs property to ecf.generic.server
props.put("service.exported.configs","ecf.generic.server");
// With two service properties, will export as a remote service via an instance of ecf.generic.server 
bundleContext.registerService(MyService.class, new MyServiceImpl(), props);

See here for a description for provider-specific service properties such as hostname, port, etc.

Bundles

org.eclipse.ecf.provider
org.eclipse.ecf.provider.remoteservice

Dependencies

org.eclipse.ecf.provider: ECF core bundles, org.eclipse.ecf.sharedobject
org.eclipse.ecf.provider.remoteservice: org.eclipse.ecf.provider, org.eclipse.ecf.remoteservice.asyncproxy

Download/Install

P2 Repo

See ECF Download Page

Karaf Feature

See ECF Download Page

Source Code

Repo

ECF Primary Git Repo

Path

org.eclipse.ecf.provider: framework/bundles/org.eclipse.ecf.provider
org.eclipse.ecf.provider.remoteservice: providers/bundles/org.eclipse.ecf.provider.remoteservice

ECF Generic Distribution Provider

r-OSGi Distribution Provider

JMS/ActiveMQ Distribution Provider

MQTT Distribution Provider

REST-based Distribution Providers

Back to the top