Difference between revisions of "EIG:Distributed EventAdmin Service"

From Eclipsepedia

Jump to: navigation, search
(Introduction)
Line 6: Line 6:
  
 
ECF's provider architecture allows the creation of a distributed EventAdmin implementation that can use a variety of wire protocols.  For example, ActiveMQ/JMS 5.2 as above, or ECF generic, XMPP, JavaGroups, commercial/proprietary messaging buses, or any others that can implement the ECF Shared Object API.
 
ECF's provider architecture allows the creation of a distributed EventAdmin implementation that can use a variety of wire protocols.  For example, ActiveMQ/JMS 5.2 as above, or ECF generic, XMPP, JavaGroups, commercial/proprietary messaging buses, or any others that can implement the ECF Shared Object API.
 +
 +
==Using the Distributed EventAdmin Service==
 +
 +
First, get ECF 3.0.  [http://www.eclipse.org/ecf/downloads.php Here is the download page].
 +
 +
Then get the two projects that implement the event admin.  Here is a project set file for them.

Revision as of 16:35, 11 June 2009

Introduction

OSGi declares an EventAdmin service that is responsible for distributing events to listeners registered via the (org.osgi.service.event.EventHandler). It's possible to create distributed implementations of such services using JMS and/or other messaging frameworks for distributing messages to other OSGi frameworks.

Distributedeventadmin.png

ECF's provider architecture allows the creation of a distributed EventAdmin implementation that can use a variety of wire protocols. For example, ActiveMQ/JMS 5.2 as above, or ECF generic, XMPP, JavaGroups, commercial/proprietary messaging buses, or any others that can implement the ECF Shared Object API.

Using the Distributed EventAdmin Service

First, get ECF 3.0. Here is the download page.

Then get the two projects that implement the event admin. Here is a project set file for them.