Composite parent = ...;
URL url = ...;

// this is your event handler instance which you can prepare via org.eclipse.e4.core.contexts.ContextInjectionFactory.inject(Object, IEclipseContext)
// you should also put the SomeGUIPart instance into the provided IEclipseContext, so it can be injected into the events handler
Object eventsHandler = ...;

Map<String, Object> options = new HashMap<String, Object>();
options.put(IXWTLoader.CONTAINER_PROPERTY, parent);
options.put(IXWTLoader.CLASS_PROPERTY, eventsHandler);
// other options
XWT.loadWithOptions(url, options);

Hi,

we're using XWT in our E4 application which works pretty good. The only problem is to get DI work in the EventHandler class we are using.

Setup looks like the following:
SomeGuiPart -> uses @PostConstruct to load XWT file and setup some fields in it
SomeGuiEventHandler -> is referenced from the XWT file using x:Class="...SomeGuiEventHandler"


The problem now is, that SomeGuiEventHandler is not part of the application model and of that no DI is available. Sadly I also don't see a way to
a) access the Eclipse context from the event handler, or
b) access the SomeGuiPart instance from the event handler, or
c) create the event handler instance in the SomeGuiPart and pass it to the XWT instance

So, the only solution I see is to handle the XWT events in the part class which is a part of the application model.

Are there better options to handle events in a separate class?

Greetings
Tobias