BundleActivator vs e4 lifeCycleURI [message #1436852] |
Fri, 03 October 2014 13:57 |
Bartosz Popiela Messages: 21 Registered: March 2012 |
Junior Member |
|
|
Hi!
1. What is the proper way to control application lifecycle in e4 based application? Should I use bundle activator (extending org.eclipse.ui.plugin.AbstractUIPlugin) or specify lifeCycleURI property in my application definition? What are the main differences between these two approaches? Is there a possibility that definied application will be started but bundle defining application will be lasy loaded and still in state STARTING (I mean that Activator.start(...) method wasn't invoked).
2. I also get the following warning for org.eclipse.e4.ui.workbench.lifecycle.PostContextCreate import: Quote:Discourage access: The type PostContextCreate is not api (...) . Is it a bug that it's x-friends restricted?
[Updated on: Fri, 03 October 2014 15:16] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02799 seconds