[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] policies wrt use of Bundle-ActivationPolicy

On 3/13/12 10:49 , Scott Lewis wrote:

ECF has consumers that use our OSGi remote services implementation in client-server use cases. Some of these also use other framework impls (e.g. felix) for the remote service host and/or consumer.

As a plugin to Eclipse, we use Bundle-ActivationPolicy: lazy for many/most of our bundles...but there are now requests [1] for us to remove BAP from some of our bundles, in order to facilitate usage in non-Eclipse use cases.

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.

-> richard

What are the current policies and/or guidelines for the use (or not) of BAP within (and/or outside of) Eclipse?



[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=373475

_______________________________________________ equinox-dev mailing list equinox-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/equinox-dev