|Re: Using e4 DI in a XWT EventHandler [message #1058137 is a reply to message #1058134]
||Sun, 12 May 2013 11:37
| Erdal Karaca
Registered: July 2009
That is currently not directly supported by XWT, but you can achieve that this way:
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>();
// other options
You should wrap the code in a util method to make it reusable (if you need that often).
Tobias P. wrote on Sun, 12 May 2013 12:59
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?
Powered by FUDForum
. Page generated in 0.15954 seconds