|Issues using the e4 bridge (@PreDestroy and @UIEventTopic in DIViewPart) [message #1078017]
||Fri, 02 August 2013 12:31
| Xander Uiterlinden
Registered: July 2009
Currently I'm investigating whether using the e4 bridge is a feasible way of migrating our Eclipse 3.7 RCP application to Eclipse 4.|
Therefore I took one of our simpler views and rewrote it to match the e4 programming model and tried the view both in a Eclipse 3.7 application using the e4 bridge as well as in an Eclipse 4 application.
The good news is all seems to be running fine in the Eclipse 4 application. The e4 bridge however seems to be lacking some functionality.
- I used DIViewPart to wrap my e4 View for Eclipse 3 use. DIViewPart does not seem to handle the @PreDestroy correctly since it only gets called on application exit rather than on closing the view. Copying the dispose() method from DIEditorPart seems to do the trick. Is there a reason it has not been implemented on DIViewPart ?
- I tried to use the @UIEventTopic annotation for handling events. Where this works fine in my Eclipse 4 application (it gets notified of all events subscribed to), in the Eclipse 3 application only one single event is received upon opening the view and all subsequent events are not offered to the handling method. A workaround is to obtain the EventBroker from the Eclipse context and subscribe there. But it would be much nicer to be able to use the @UIEventTopic annotation instead.
Please let me know if I can be of any assistance in solving these issues.
Powered by FUDForum
. Page generated in 0.01855 seconds