This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Allow OSGi bundles to specify their start level | ||
---|---|---|---|
Product: | platform | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Netigso | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | apireviews, jglick, sserban |
Priority: | P1 | Keywords: | API_REVIEW_FAST |
Version: | 7.1 | ||
Hardware: | Other | ||
OS: | Linux | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: | startlevel and FRAMEWORK_START_LEVEL APIs |
Need #NOI18N before nonlocalizable keys. I'll use NOI18N and integrate tomorrow. ergonomics#c6e6d03ae352 Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/c6e6d03ae352 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #201796: config/Modules/*.xml files may contain specification of start level for OSGi bundles. Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/33b558b21865 User: Jaroslav Tulach <jtulach@netbeans.org> Log: Addition to #201796: Allow the application to specify that bundles with high startlevel should not be 'started' at all |
Created attachment 110520 [details] startlevel and FRAMEWORK_START_LEVEL APIs Standard OSGi way to control enablement of bundles is to assign them different startlevel. So far the Netigso system has cared about the startlevels at all, but it is time to change that. As a result some OSGi bundles may be registered as enabled="true" and yet their BundleActivator.start() may not be called on start.