Hi Thomas,
FWIW there was quite a lot of discussion and public review of this API
as part of the original contribution. The history is here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=253777
I've opened this bug to track the graduation request:
https://bugs.eclipse.org/bugs/show_bug.cgi?
Hi Scott,
I am glad to hear you have been making good use of the concurrent.future
package in ECF. Unfortunately I don't see us being able to commit to fully
reviewing the API in the last two weeks of M7 to allow it to become API for
Helios. This will have to wait until the next release. Pleas
Lazar,
Please open a bug against Equinox.
Tom
|>
| From: |
|>
>--|
|"Richard S. Hall"
On 4/14/10 10:48, Kirchev, Lazar wrote:
This is exactly the problem - the system bundle is put in state ACTIVE before
starting the bundles, which should be initially started, and the event is fired
after starting the bundles. So when the state is ACTIVE we cannot be sure if
this is before, or
This is exactly the problem - the system bundle is put in state ACTIVE before
starting the bundles, which should be initially started, and the event is fired
after starting the bundles. So when the state is ACTIVE we cannot be sure if
this is before, or after the event is fired.
Regards,
Lazar
On 4/14/10 10:09, Kirchev, Lazar wrote:
Yes, we could use FrameworkEvent.STARTED, but only if we are sure that
we listen for this event when it is fired. If the code, which listens
for it, is executed after the framework is started, then it will never
get the event. This happens in an Activat
Yes, we could use FrameworkEvent.STARTED, but only if we are sure that we
listen for this event when it is fired. If the code, which listens for it, is
executed after the framework is started, then it will never get the event. This
happens in an Activator of a bundle – it may be executed during
Yes, you should use the FrameworkEvent.STARTED event for this. You should
probably open a bug so we can investigate the current behavior anyway to
see if the comment is valid.
Tom
|>
| From: |
|>
>
We don't you just wait for the FrameworkEvent.STARTED event?
* This event is fired when the Framework has started after all
installed
* bundles that are marked to be started have been started and the
Framework
* has reached the initial start level. The source of this e
Hello,
We are implementing logic which depends on the system bundle being put in
ACTIVE state after all bundles, which should be running, are started. However,
it turned out that actually the system bundle is put in ACTIVE state just
before the bundles are started. This is evident from the meth
10 matches
Mail list logo
