Re: [equinox-dev] policies wrt use of Bundle-ActivationPolicy

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

Hi Richard,

On 3/13/2012 9:40 AM, Richard S. Hall wrote:
> <stuff deleted>

> 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 
[1] is where the bundles are being started via

bundle.start(Bundle.START_ACTIVATION_POLICY)

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?

Thanks,

Scott