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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

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

From: Glyn Normington <gnormington@xxxxxxxxxx>
Date: Fri, 5 Nov 2010 10:12:10 -0700
Accept-language: en-US
Acceptlanguage: en-US
Delivered-to: jetty-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jetty-dev>
List-help: <mailto:jetty-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jetty-dev>, <mailto:jetty-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jetty-dev>, <mailto:jetty-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: Act9DJUKVu9KlUjZTgOgC90KEWX0aw==
Thread-topic: 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.

Regards,
Glyn

Follow-Ups:
- Re: [jetty-dev] Lazy activation of osgi.boot bundle
  - From: Hugues Malphettes

Prev by Date: Re: [jetty-dev] Jetty OSGi bundles
Next by Date: Re: [jetty-dev] Lazy activation of osgi.boot bundle
Previous by thread: [jetty-dev] jetty-7.2.0.v20101020 build failure
Next by thread: Re: [jetty-dev] Lazy activation of osgi.boot bundle
Index(es):
- Date
- Thread

Breadcrumbs