I think the behavior you are seeing is because the bundle has not been
marked for activation using its activation policy. See Bundle.start(int)
for details on how a bundle should be persistently marked for activation
with its activation policy. The behavior you see is expected if you have
not ever called Bundle.start method.
Tom
From: "Guillaume Sauthier (OW2)" <[email protected]>
To: OSGi Developer Mail List <[email protected]>,
Date: 01/11/2012 10:34 AM
Subject: [osgi-dev] Re: Bundle ActivationPolicy question
With Felix, we experienced that the Bundle triggering the class load can
use the class loaded from the lazy Bundle, but the lazy Bundle was not
activated after the class was loaded...
--G
2012/1/11 Guillaume Sauthier (OW2) <[email protected]>
Hi all
What happen when a Bundle with Bundle-ActivationPolicy: lazy in its
Manifest is being used while in the RESOLVED state ?
In other words, the Bundle has not yet been started with Bundle.start
(START_LAZY_ACTIVATION), but another Bundle is being activated and is
using a class from the lazy Bundle.
The examples I found on the OSGi web site are only explaining behaviors
when the lazy bundle is activated because of a Bundle.loadClass() while
in STARTING state.
Thanks
--G
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
