Re: [jetty-dev] Lazy activation of osgi.boot bundle

[Hugues Malphettes <hmalphettes@xxxxxxxxxxx>]

On Fri, Nov 5, 2010 at 10:12 AM, Glyn Normington <gnormington@xxxxxxxxxx> wrote:

I don't understand why the Jetty osgi.boot bundle has lazy start specified. Lazy start bundles are intended to move from STARTING to ACTIVE when a class is loaded from the bundle's class loader. It seems that the osgi.boot bundle is not typically moved to ACTIVE by such a class load and it is necessary to use Bundle.start again to force it to ACTIVE.

Hum that is weird or maybe I misunderstood what is happening.

Do you recommend that we remove the lazy start?

Or did you observe that the bundle would not be marked active even though one of its classes is loaded?

Thanks,

Hugues

 

This make it awkward to use in a Virgo environment, but I think the same issue is true in a number of environments including raw Equinox.

Regards,
Glyn

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