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.
Difference between revisions of "Distribution Providers"
(→Distribution Providers) |
|||
Line 21: | Line 21: | ||
==Distribution Providers== | ==Distribution Providers== | ||
− | Generic Provider | + | ===Generic Provider=== |
− | OSGi Configuration Types/ECF Container Types | + | OSGi Configuration Types/ECF Container Types |
− | < | + | <br><br> |
− | < | + | ecf.generic.server<br> |
− | + | ecf.generic.client<br> | |
− | + | ecf.generic.ssl.server<br> | |
− | + | ecf.generic.ssl.client<br> | |
− | + | ||
For example, to export an instance of MyServiceImpl | For example, to export an instance of MyServiceImpl | ||
Line 42: | Line 41: | ||
</pre> | </pre> | ||
− | + | [[ECF_Generic_Provider_Configuration_Properties#Remote_Service_Configuration_Properties | See here ]] for a description for provider-specific service properties. | |
− | Bundles: org.eclipse.ecf.provider, org.eclipse.ecf.provider.remoteservice | + | Bundles: org.eclipse.ecf.provider, org.eclipse.ecf.provider.remoteservice<br> |
− | Dependencies | + | <br> |
− | < | + | Dependencies |
− | < | + | <br><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<br> |
+ | <br> | ||
[[ECF Generic Distribution Provider]] | [[ECF Generic Distribution Provider]] |
Revision as of 16:47, 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
- Framework: OSGi R5+
- ECF Core: org.eclipse.ecf, org.eclipse.ecf.identity
- org.eclipse.equinox.concurrent.future bundle
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.
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
ECF Generic Distribution Provider