[Wrapper-user] WrapperManager.signalStarting()

[Bernd L. <Ber...@we...>]

Hi,

i have two questions with the above method:

1. I discovered, as this method is synchronized, I cannot call the 
signalStarting from within a spawned thread while the application 
starts. While I use integration method 3, when debugging in Eclipse I 
start it using the main method of the main class, so the main thread 
is holding the lock due to WrapperManager.start(new MyApp(), args). At 
the moment I have a static boolean "startedFromMain" that is checked 
everywhere. Any hints for a better approach?

2. The comment from Leif with the signalStarting/signalStopping issue 
with rounding down the millis: "The 3.2.4 release has been modified so 
that the signalStarting and signalStopping methods will now only 
extend a timeout rather than potentially having the effect of 
shortening it."

As the start/stop time of my application can differ very much, I want 
to give the user a hint, so I start with a pessimistic value (say long 
time) and as the startup phase continues, I calculate more precisely 
and probably the time shortens. Is this still possible or is the first 
value ("It takes half an hour") now my deadline? If this is the case, 
I have to rearrange with an optimistic start value and extend the 
timeout during application start/stop.

Bernd