[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] policies wrt use of Bundle-ActivationPolicy
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Tue, 13 Mar 2012 11:45:10 -0700
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
On 3/13/2012 9:40 AM, Richard S. Hall wrote:
To be clear, this has nothing to do with running on other framework
impls, it is an artifact of using a lazy activation policy. If you
have a bundle that is lazy and other bundles are waiting for it to do
something in order to proceed and they do not trigger a class load on
the lazy bundle, then they will wait forever. This is true on any OSGi
framework since R4.1.
Thanks Richard...that's understood (by me). The use case described in
 is where the bundles are being started via
which, if the bundle has BAP: lazy set (as many of our bundles currently
do), then the bundle is not actually started by this call (on whatever
framework). This is the behavior that the bug author wants changed (via
removal of BAP: lazy)...for some of our remote service impl bundles.
So my main question is: what are Equinox's (Eclipse's)
policies/guidelines/requirements WRT BAP: lazy usage?