Skip to main content
Jump to: navigation, search

EIG:Runtime Dependencies/Configuration

Revision as of 15:18, 12 February 2011 by Mpetzold.gmx.net (Talk | contribs) (ECF Discovery Provider Bundles)

Installation of ECF

The ECF 3.2 Remote Services implementation depends upon some bundles included in Eclipse 3.6, so you should download and use (at least) Eclipse 3.6M5 SDK. You can download Eclipse3.6M5 SDK here or a more recent version from the Eclipse 3.6 stream here.

The ECF Remote Services bundles are included in the ECF SDK, which can be downloaded or installed via Marketplace or p2.

Installation via Marketplace

[...]

Installation via p2

[...]

Adding ECF to the Target Platform

When developing with Eclipse 3.5 or newer, it's possible to use a concept called a target platform. The target platform specifies the set of bundles used to compile and build against within the Eclipse PDE (plugin development environment). The default target platform is Eclipse itself, but the target platform can be set to any desired set of bundles. One way to develop applications that use some or all of ECF is to add the ECF SDK to your target platform. Then you are able to develop against and build using ECF functionality.

  1. Select from Menu: Window->Preferences->Plug-in Development->Target Platform
  2. Choose Add... button
  3. Initialize the Target Definition with Default: Default target for the running platform
  4. Specify Name: ECF 3.2 SDK
  5. Choose Add... button
  6. Select Software Site and Next>
  7. Choose Add... button
  8. In Add Repository dialog
    1. Name: ECF 3.2 SDK
    2. Location: http://www.eclipse.org/external/rt/ecf/3.2/3.6/site.p2
  9. Choose OK
  10. Open the ECF tree item
  11. Select the Eclipse Communication Framework SDK check box
  12. Unselect Include Required Software. This option should not be selected.
  13. Choose Finish
  14. Select the target platform you just created (i.e. ECF 3.2 SDK)
  15. Choose OK

Your target platform should then be set to your current Eclipse, plus the ECF SDK. Then you can refer to ECF classes in your own bundles/plugins.

OSGi Remote Service Bundles

If the ECF SDK is installed into Eclipse, then the ECF Remote Services bundles are installed, but also a number of Eclipse views and perspectives are made available for use within Eclipse. If you only would like to use the bundles of the OSGi Remote Service implementation, take these:

ECF Bundles (OSGi Remote Service Implementation)

Bundle Description
org.eclipse.ecf ECF Core Bundle
org.eclipse.ecf.discovery
org.eclipse.ecf.identity
org.eclipse.ecf.osgi.services.discovery Implementation of the OSGi Discovery API.
org.eclipse.ecf.osgi.services.distribution Implementation of the OSGi Distribution API.
org.eclipse.ecf.osgi.services.remoteserviceadmin Implementation of the OSGi Remote Service and Remote Service Admin API.
org.eclipse.ecf.provider
org.eclipse.ecf.remoteservice
org.eclipse.ecf.sharedobject

ECF Distribution Provider Bundles

In a common use case you should choose only one(!) of these providers.

Bundle Description
org.eclipse.ecf.provider.remoteservice Generic provider ("ecf.generic.client" and "ecf.generic.server").
org.eclipse.ecf.provider.r_osgi R-OSGi Provider ("ecf.r_osgi.peer")

ECF Discovery Provider Bundles

In a common use case you should choose only one(!) of these providers.

Bundle Description
org.eclipse.ecf.provider.jmdns Zeroconf/Bonjour Provider
org.eclipse.ecf.provider.jslp SLP Provider
org.eclipse.ecf.provider.localdiscovery
org.eclipse.ecf.provider.zookeeper ZooDiscovery Provider

Other Bundles

Bundle Description
ch.ethz.iks.r_osgi.remote Is only required when using org.eclipse.ecf.provider.r_osgi
ch.ethz.iks.slp Is only required when using org.eclipse.ecf.provider.jslp
org.apache.zookeeper Is only required when using org.eclipse.ecf.provider.zookeeper
org.objectweb.asm Java bytecode manipulation and analysis framework.

Back to the top