[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [corona-dev] PROBLEM: OSGi events does not arrive when bundleis being activated.
|
Stepping back. Turned out to be probably my bug somewhere. They asked me
to give a simple example, so I did a sample plugin that would work in
this way. Unfortunatelly it worked fine.
Marcin
O'Flynn, Dennis napisał(a):
Do you know what event service bug?
Please update any of our Corona Bugz items that depend on this bug being fixed.
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: Monday, January 15, 2007 4:21 AM
To: Corona development
Subject: Re: [corona-dev] PROBLEM: OSGi events does not arrive when bundleis being activated.
Turned out to be an event service BUG.
Marcin
Marcin Okraszewski napisał(a):
I have a problem with OSGi events. The problem is connected with issue
#166497 about logging management. After a conversation with Dennis we
got to point that the best way to control our logging architecture
internally are events.
My observation is: events are not delivered to event handles of
bundles that are being activated. In other words you wan't receive an
event when your bundle is still in Activator.start() method.
Do you have any idea if it can be controlled in any way? I couldn't
find it in OSGi spec at all.
Marcin
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it.
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.