|Re: [jetty-dev] Lazy activation of osgi.boot bundle|
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.
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.
jetty-dev mailing list
Back to the top