Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Riena/Getting Started with injecting services and extensions


Riena ProjectGetting Started ▶ Injecting Services and Extensions

The Idea of Injecting Services and Extensions in Riena

Services and extensions are the main building blocks of Eclipse RCP applications. There is a long list of discussions and debates about when to use services and when to use extensions. So, we will not add another discussion here. We think that both are useful and have their uses.

Both approaches require a lot of code for respecting their life cycle, which is prone to errors. Most of this code is embedded within the code that needs other services or extensions, like models, which one might prefer to be simple POJOs. Concerns are not clearly separated, and unit testing is more difficult.

Dependency injection frameworks such as Spring or HiveMind are commonly used to counter this problem. With Riena we offer a simpler approach to injecting both services and extensions into objects (pojos). The advantages:

  • code-based, i.e. no XML configuration files
  • fluent interfaces
  • conventions that simplify the injection definitions.

Injecting Services

The service injection allows to inject services into target objects (pojos). The selection of the services to be injected can either be done by service ranking or by using a filter expression.

Using service ranking

Service ranking is a property of a service that can be supplied when registering a service. The default service ranking (i.e. when it is not supplied) is 0. Riena defines most of its services with a ranking of -100. This has the effect that services without a specified ranking (thus using the default ranking) will override a Riena service.


or shorter


where target is the pojo into which the service shall be injected. In this example, target could be a Customer model.

Within the target we need to implement the binding and unbinding methods, which both take an instance of the injected service's type as their only parameter. Since we did not specify any custom method names, Riena expects the two methods to be named "bind" and "unbind", respectively:

public void bind(ICustomerSearch service) {
	this.service = service;
public void unbind(ICustomerSearch service) {
	this.service = null;

Using filters

The other possibility is to use an RFC 1960-based filter expression to select the services to be injected.


The andStart(...) method starts the injector. From now on the service injector will track the specified services, and when services come and go they will be injected into or removed from the pojos. The method names for injecting/removing can be specified with the bind("myBindMethod") and unbind("myUnbindMethod") methods. If they are not defined, default method names will be used, currently "bind" and "unbind", which is why we needed to implement the two methods with these names in the target, see listing above.

When service ranking is used, at most one service will be injected. When the filter-based approach is used, multiple services or none can be injected. In the case of multiple services, the bind/unbind methods will be called multiple times; the target object must keep track of the services injected.

To stop the injection, it is possible to call the stop() method on the injector at any time. This causes all injected services to be unbound. However, when a bundle associated with an injector via the andStart(...) method stops, all injected services will be stopped as well.

Syntax summary / Cheatsheet

.service( IMyService.class | "org.eclipse.myproject.IMyService" )
[.useRanking() | .useFilter("(remote=true)") ]

Injecting Extensions

Extensions get injected into pojos as instances of an interface. The interfaces need only declare the getters. Dynamic proxies will be created for the interfaces which map the data from the extensions. A few simple rules are used for the mapping from extensions to the interfaces (lightweight XML/Java mapping). Extension properties. i.e. attributes, sub-elements and element value can then accessed by getters in the interface definition. It is only necessary to define the interfaces for the mapping.

Conformity to the extension schema

The extension injector does not evaluate the extension schema, so it can only trust that the extension and the interface match with regards to a few basic rules:

  • One interface maps to one extension element type.
  • The interface must be annotated with @ExtensionInterface.
  • Interface methods can contain getters prefixed with:
    • get...
    • is...
    • create...
  • Such prefixed methods enforce a default mapping to attribute or element names, i.e. the remainder of the methods name is interpreted as the attribute or element name. Simple name mangling is performed, e.g for the method getDatabaseURL() the mapping looks for the attribute named databaseURL.
To enforce another name mapping a method can be annotated with @MapName("name"). The name specifies the name of the element or attribute. The extension element's content can be retrieved by annotating the method with @MapContent(). The return type must be String. The method names of such annotated methods can be arbitrary.
  • The return type of a method indicates how the value of an attribute will be converted. If the return type is
    a primitive type or java.lang.String 
    then the mapping converts the attribute's value to the corresponding type.
    an interface or an array of interfaces annotated with @ExtensionInterface 
    then the mapping tries to resolve to a nested element or to nested elements.
    then the method returns the contributing bundle.
    then the attribute is interpreted as a class name and a class instance will be returned.
    and finally, if none of the above matches 
    the mapping tries to create an new instance of the attribute's value (interpreted as class name) each time it is called. If the extension attribute is not defined null will be returned.

Examples of extension injection

This is how you would inject an extension into a pojo target:


A sample interface from Riena:

 * Interface for a SubModule extension that defines how an activated submodule
 * appears in the work area.
public interface ISubModuleExtension {
	 * @return A controller that controlles the UI widgets in the view through
	 *         ridgets (see org.eclipse.riena.ui.internal.ridgets.IRidget)
	IController createController();
	 * Indicates whether the view is shared i.e. whether one instance of the
	 * view should be used for all submodule instances.
	 * @return true if the specified view should be a shared view, false
	 *         otherwise
	boolean isShared();
	 * @return For the SWT-based Riena UI this is the ID of the view associated
	 *         with the submodule. Must match the ID field of an
	 *         "org.eclipse.ui.view" extension.
	String getView();
	 * Return the contributing bundle of the extension.
	 * @return The contributing bundle
	Bundle getContributingBundle();
	 * @return The type part of the ID of a navigation node.
	 * @see NavigationNodeId#getTypeId()
	String getTypeId();

By executing:


where target is an instance of SubModuleExtensionInjectionHelper, the extension gets injected into:

public class SubModuleExtensionInjectionHelper {
	private ISubModuleExtension[] data;
	public void update(ISubModuleExtension[] data) { = data.clone();
	public ISubModuleExtension[] getData() {
		return data.clone();

Syntax summary / Cheatsheet

.extension( ["org.eclipse.myproject.myExtensionPointId"] )
[.expectingExactly(int) | .expectingMinMax(int, int)]

The above is incomplete, it does not show all the possible ways of configuring and using extension injection. It is merely intended as a rough guide. Look up the Javadoc in ExtensionDescriptor for documentation on heterogeneous(), isHomogeneous(), getMin/MaxOccurrences(), requiresArrayUpdateMethod(), and in ExtensionInjector for specific(), doNotReplaceSymbols().

Next: Wiring

See how you can avoid using Inject.… sentences in your controllers by using Riena's Wiring mechanism.

Back to the top