[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Is earlyStartup == lateStartup
|
One concern with this is related to how startup() is called. The startup()
method is called from within synchronized classloader code, which makes it
vulnerable to deadlock. For this reason there are restrictions on what can
be done in the startup() method. See the various notes in the javadoc for
Plugin.startup() for more details (also bugs 5875, 12827). The short
summary is that startup() shouldn't do anything fancy. There are no such
restrictions for the earlyStartup() method. I don't know if this was the
reasoning behind having the extra method, but it's something to keep in
mind.
"Dirk Baeumer"
<Dirk_Baeumer@xxxxxxx> To: platform-ui-dev@xxxxxxxxxxx
Sent by: cc:
platform-ui-dev-admin@ Subject: [platform-ui-dev] Is earlyStartup == lateStartup
eclipse.org
07/10/2002 05:58 AM
Please respond to
platform-ui-dev
I am currently experimenting with adding another webapp to eclipse. Since I
must ensure that the webapp is running
right from the beginning my plugin implements IStartup and defines the
corresponding extension point. While testing
the plugin I found out that both first startup and then earlyStartup is
called on the plugin and both method calls occur
in the same separate thread.
What is the rational behind having earlyStartup? Would it be enough to only
call startup() ? Then we could remove
IStartup and only need the extension point which would make it easier to
understand.
Dirk
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
