On 12/27/2010 10:43 PM, Bhumana, Kiran wrote:
But what does that mean/imply in terms of usage. What happens if I try
to use a class from such a bundle? The class will be loaded but the
bundle will still not be activated -- meaning this is similar behavior
to a bundle that doesn't have activator but just exports packages
(like a library bundle use case) ?
Yes.
Are there other use cases?
No.
-> richard
Thanks,
Kiran.
*From:*[email protected]
[mailto:[email protected]] *On Behalf Of *Richard S. Hall
*Sent:* Monday, December 27, 2010 7:25 PM
*To:* OSGi Developer Mail List
*Subject:* Re: [osgi-dev] Bundle-ActivationPolicy: exclude directive
On 12/27/2010 10:12 PM, Bhumana, Kiran wrote:
Referring to r4.core spec; In section 4.4.6.2 that describes lazy
activation policy, there is an "exclude" directive (list of classes)
that can be provided . What does it mean? How is it expected to be used?
I believe it is used to exclude classes from triggering activation
when they are loaded. By default any class load from a lazily started
bundle will trigger class loading.
-> richard
**
*Thanks,*
-Kiran
**
_______________________________________________
OSGi Developer Mail List
[email protected] <mailto:[email protected]>
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
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
