Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] Lazy activation of osgi.boot bundle

I recommend you remove the lazy start.

I think class loading out of osgi.boot *would* trigger the transition from STARTING to ACTIVE, but I don't see that as a good use case as the next thing that is likely to happen after the osgi.boot has got to STARTING is that someone will start a web application bundle and hope that the Jetty RFC 66 extender will notice (and no class load from osgi.boot will have happened).


On 5 Nov 2010, at 17:18, Hugues Malphettes wrote:

On Fri, Nov 5, 2010 at 10:12 AM, Glyn Normington <gnormington@xxxxxxxxxx<mailto: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?

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