Skip to main content
Jump to: navigation, search

SOAP-based Providers

With ECF 3.2, one can create client providers that implement SOAP-based protocols.

Below is an example of doing this for an existing SOAP-based dictionary service available on the internet.

The dictionary service is described 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 service will be implemented). The Web Service Description Language description of this service is available here.

The example is currently located on


These three example bundles 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);

This IDictionary interface and the WordDefinition class are the entire contents of the bundle o.e.e.examples.remoteservices.dictionary.common. These two classes define the service API.

1. Create the provider bundle (i.e. the example is called o.e.e.provider.dictionary.soap.client).

2. Using the dictionary service wsdl, and either the Apache Axis wsdl2java OR the WTP Web Client Wizard (which, incidently, also uses Apache Axis' wsdl2java generator), generate the client java code into the new provider bundle. Also, to get the generated code to compile in the bundle, you will add the supporting Axis libraries to the bundle, and then make these libraries available on the Bundle-Classpath in the bundle's For example, here is part of the for the example provider:

Bundle-ClassPath: lib/axis.jar,

These libraries are available in the Apache Axis 1.4 distribution.

3. Create a new class that extends org.eclipse.ecf.remoteservice.soap.client.AbstractSoapClientContainer. In the example provider, this is the DictionarySoapClientContainer class.

4. Create a new class in the provider bundle that extends the class org.eclipse.ecf.remoteservice.soap.client.AbstractSoapClientService. In the example provider, this is the DictionarySoapClientService.

5. Create a new class that extends org.eclipse.ecf.core.provider.BaseContainerInstantiator. In the example provider this is the DictionarySoapClientContainerInstantiator.

See the examples in the o.e.e.provider.dictionary.soap.client bundle for understanding the implementation.

6. Create an extension for the ECF 'containerFactory' extension point, and have it point to the container instantiator class you created...for example


At this point, if all the Axis supporting libraries are on the Bundle-Classpath, and the abstract methods have been appropriately implemented, then you are done.

The test bundle org.eclipse.ecf.examples.tests.remoteservices.dictionary.soap.client has a junit test case that shows the use of the newly created provider to use the IDictionary remote service proxy.

Here, for example, is some test code that shows the use of the ECF IDictionary remote service:

 	protected void setUp() throws Exception {
 		container = getContainerFactory().createContainer("ecf.examples.dictionary.soap.client");
 		containerAdapter = (IRemoteServiceContainerAdapter) container.getAdapter(IRemoteServiceContainerAdapter.class);
 	public void testDictionaryService() throws Exception {
 		IRemoteServiceReference[] refs = containerAdapter.getRemoteServiceReferences((ID) null, IDictionary.class.getName(), null);
 		assertTrue(refs.length > 0);
 		IRemoteService remoteService = containerAdapter.getRemoteService(refs[0]);
 		// Get proxy
 		IDictionary dictionary = (IDictionary) remoteService.getProxy();
 		// Now call it
 		WordDefinition def = dictionary.define("abstruse");

Back to the top