Jump to: navigation, search

Eclipse4/RCP/Event Model

Stop.png
This page is a stub
This page is currently undergoing substantial and active editing. Please refrain from editing this page or raising issues against this page until this banner is gone. Hopefully later today. :-)


Eclipse 4 uses a publish/subscribe event model. The rational for using this strategy is described in Event Processing in E4.

Eclipse 4 implements a global event bus on top of the OSGi eventing engine. The global event bus is accessed using IEventBroker (org.eclipse.e4.core.services.events.IEventBroker) which provides methods for subscribing and unsbubscribing to events on the bus, as well as methods for posting events to the bus.

An instance of the IEventBroker is typically available in the EclipseContext:

…
 
private IEclipseContext ecliseContext;
 
…
 
IEventBroker eventBroker = eclipseContext.get(IEventBroker.class);

or is provided via dependancy injection.

@Inject
IEventBroker eventBroker;

Posting an Event

Putting an event on the global event bus is as simple as calling IEventBroker.post(String topic, Object data) for events that should be delivered asynchronously or IEventBroker.send(String topic, Object data) for events that should be delivered synchronously.

...
foo.Bar payload = getPayload();
boolean wasDispatchedSuccessfully = eventBroker.send(TOPIC_STRING, payload);

If the payload of the send command is a plain old Java object, then the payload is attached to the event OSGi Event as a property with the key IEventBroker.DATA. If payload is a Dictionary or a MAP, all the values are added

Responding to Events

There are two ways to be notified of events:

   Dependency Injection using @UIEventTopic
   Subscribing to the event using IEventBroker.subscribe()


Whenever possible you should use dependency injection. This results in code that is easier to read an maintain with fewer anonymous inner classes.

In each example below we show how to receive the event and data pushed in the Posting an Event example above.

Dependency Injection

@Inject @Optional
public void closeHandler(@UIEventTopic(TOPIC_STRING) foo.Bar payload) {
    // Useful work that has access to payload.  The instance of foo.Bar that the event poster placed on the global event bus with the topic TOPIC_STRING
}

Subscribing using IEventBroker

IEventBroker eventBroker;void addSubscribers() {
 
eventBroker.subscribe(TOPIC_STRING, closeHandler);
 
…
}
 
void removeSubscribers() {
    eventBroker.unsubscribe(closeHandler);}
 
…
 
private EventHandler closeHandler = new EventHandler() {
    public void handleEvent(Event event) {
 
    // Useful work that has access
    foo.Bar payload = (foo.Bar) event.getProperty(IEventBroker.DATA);
}

UI Model Events

The Eclipse 4 UI is a model based UI built on an underlying EMF Model. Part of the UI framework listens to EMF events and publishes UIEvents on the global event bus.

The chief class of interest is org.eclipse.e4.ui.workbench.UIEvents. This class defines all the topic and attribute strings used to subscribe and respond to the various UI events through either of the two mechanisms described above.

The bulk of the constants in this class are generated directly from the EMF model at development time using the utility org.eclipse.e4.ui.internal.workbench.swt.GenTopic. There are a few hand crafted constants for non UI events such as the Lifecycle events.

Late in the M4 milestone the hierarchy and usage pattern of UIEvents underwent a significant change. This page will discuss the new mechanism. For a discussion of the old mechanism and the changes you need to make to migrate from the old style to the new style see this [page]

UIEvent Structure

Each EMF model element will have a corresponding inner interface defined in UIEvents. Each interface has two constants defined for each attribute of the corresponding model element.

Here is the example for the UILabel model element

    @SuppressWarnings("javadoc")
   public static interface UILabel {
 
       // Topics that can be subscribed to
 
       @Deprecated
       public static final String ALL = "org/eclipse/e4/ui/model/ui/UILabel"; //$NON-NLS-1$
 
       public static final String TOPIC_ALL = "org/eclipse/e4/ui/model/ui/UILabel/*"; //$NON-NLS-1$
       public static final String TOPIC_ICONURI = "org/eclipse/e4/ui/model/ui/UILabel/iconURI/*"; //$NON-NLS-1$
       public static final String TOPIC_LABEL = "org/eclipse/e4/ui/model/ui/UILabel/label/*"; //$NON-NLS-1$
       public static final String TOPIC_TOOLTIP = "org/eclipse/e4/ui/model/ui/UILabel/tooltip/*"; //$NON-NLS-1$
 
       // Attributes that can be tested in event handlers
       public static final String ICONURI = "iconURI"; //$NON-NLS-1$
       public static final String LABEL = "label"; //$NON-NLS-1$
       public static final String TOOLTIP = "tooltip"; //$NON-NLS-1$
   }

The TOPIC_* constants are used to subscribe to events generated when the corresponding attribute changes. The constant can be used for either the dependancy injection technique or the IEventBroker.subscribe() technique described above. The TOPIC_ALL constant is used to register for changes on all the attributes of a model element.

The constants named directly for the element attribute (LABEL, TOOLTIP and ICONURI from the example above) are used in the event handlers themselves if you need to inspect the event and determine which attributes have actually changed.

This works because UIEventPublisher adds the attribute name from the source EMF event to the OSGi event with the property key UIEvents.EventTags.ATTNAME. The other UIEvents.EventTags.* constants list other values that may be published in an event depending on the event type. Different event types will store differnt tags in the event.