Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search


< Eclipse4‎ | API

Services and Context Values

This section will describe which elements are guaranteed to be available for injection through the IEclipseContext. The most common of these will be the 'standard' services but will also reference some other 'value' elements (i.e. the injected value is *not* an interface itself but some discreet value such as a preference or model event).

Basic Services


This service presents API appropriate for working with the UI Model. If contains methods to search for model elements via a variety of search parameters a well as operations that can be used to manipulate the model to achieve changes in the UI.


This service provides API that deals with the runtime aspects of managin the current workbench UI such as opening new parts or getting / setting the 'active' part...

Can currently NOT used to open new parts as you cannot define the container, see


This service allows manipulation of the key binding structures.

This services is used by the model to push key bindings into the runtime. It needs polish and I don't think it should be API for Kepler.


Provides API to control the active 'chain' within a context structure.

The EContextService is important to programmatic clients, for activating contexts in their @PostConstruct or managing context activations based on the state of their controls (which widgets have focus, etc).


Provides API to construct Commands.

ECommandService allows interaction with the Command API, accessing commands and creating parameterized commands for execution. It's like a global dictionary.


This provides API to manage Handlers.

The ParameterizedCommand contains the information of what to execute (i.e. it comes from the MenuItem or ToolItem or KeyBinding). The EHandlerService must then look up the handler to execute and actually execute it. The ECommandService is for managing commands, but it knows nothing of handlers.
getContext() is used in the ContributedAction, but it is cast to the implementation. It could probably be removed.


Provides a single API to register context menus.

This method is used to instantiate an MPopupMenu and hook it up to the parent Control that's passed in. Contribution classes (MParts) need access to this. This should wait until after Kepler, as it probably could be replaced with some work and having the MPart call presentationEngine.createGui(mPopupMenu, control, mPart.getContext())


This allows for registration of listeners regarding the current selection. Note that this has more functionality in it than the @Inject approach since it provides 'post selection' (i.e. deferred) listeners as well as regular listeners.


Allows access to the OSGI event broker and can be used to register / unregister listeners on the UIModel.

Note that this API is incomplete, as it doesn't allow you to unregister an EventHandler from a specific topic

Back to the top