Difference between revisions of "ECF/REST abstraction"
(→OSGi Services for Rest Clients) |
(→OSGi Services for REST Clients) |
||
| Line 1: | Line 1: | ||
| − | ==OSGi Services | + | ==OSGi Services to expose REST Clients== |
ECF's focus has been the support of OSGi remote services...i.e. exposing OSGi services remotely, via proxies that have underneath them some protocol for communicating with the actual remote service. | ECF's focus has been the support of OSGi remote services...i.e. exposing OSGi services remotely, via proxies that have underneath them some protocol for communicating with the actual remote service. | ||
Revision as of 14:32, 14 March 2011
OSGi Services to expose REST Clients
ECF's focus has been the support of OSGi remote services...i.e. exposing OSGi services remotely, via proxies that have underneath them some protocol for communicating with the actual remote service.
REST-based services use http to access remote resources via http get, put, post, and delete actions.
The ECF REST abstraction allows REST-based services to be exposed to clients/consumers as OSGi services. This allows the automatic use of a number of useful technologies based upon OSGi services (e.g. declarative services, spring, ServiceTracker, etc) for accessing REST-based services.
UNDER CONSTRUCTION
Test/Example code
See the test cases in org.eclipse.ecf.tests.remoteservice.rest. Particularly the test classes: org.eclipse.ecf.tests.remoteservice.rest.RestRemoteServiceTest and org.eclipse.ecf.tests.remoteservice.rest.twitter.TwitterRemoteServiceTest.
Javadocs
Documentation is available in pse.ecf Javadoc API. The REST client API is in these packages:
- org.eclipse.ecf.remoteservice.rest
- org.eclipse.ecf.remoteservice.rest.client
- org.eclipse.ecf.remoteservice.rest.identity
- org.eclipse.ecf.remoteservice.rest.util