Difference between revisions of "SOAP-based Providers"

Revision as of 00:23, 17 January 2010

With ECF 3.2, it's possible to easily create client providers that implement SOAP-based protocols.

Below is an example of doing this for an existing SOAP-based dictionary service.

First, the dictionary service is located here. It's a simple dictionary service...given a word, it returns the definitions available for that word (there are other functions in the API, but for the purposes of simplifying this example only the definition retrieval service will be implemented). The Web Service Discription Language description of this service is available here.

The example is currently located on the ECF OSUOSL site. Here's the CVS information for this site:

anonymous:  :pserver:anonymous@ecf1.osuosl.org:/ecf

extssh:  :extssh:ecf1.osuosl.org:/home/cvs/ecf

modules:

examples/bundles/org.eclipse.ecf.examples.remoteservices.dictionary.common examples/bundles/org.eclipse.ecf.examples.provider.dictionary.soap.client examples/bundles/org.eclipse.ecf.examples.tests.remoteservices.dictionary.soap.client

These depend upon several of the ECF sdk bundles, these can be retrieved via the instructions on this page.

Below is a short description of how this provider was created.

1. Define the service API and create a 'common' bundle for it. If the dictionary service, the dictionary OSGi service was defined as

public interface IDictionary {

	public WordDefinition define(String word);
	
}