NetBeans Architecture Answers for NetBeans OSGi Integration module


Interfaces table

Group of java interfaces
Interface NameIn/OutStabilitySpecified in What Document?
NetigsoExportedUnder Development

the heart of NetBeans integration with OSGi with NetBeans module system is contained in this module. This module locates the OSGi framework implmentation and is then responsible for finding, registering and starting OSGi bundles provided by the NetBeans module system.

ExceptionAnnotatableUsingLogRecordsImportedFriend

The module is needed for compilation. The module is used during runtime. Specification version 2.50 is required.

org.netbeans.core.startupImportedPrivate

The module is needed for compilation. The module is used during runtime. Specification version 1.60 is required.

org.netbeans.libs.osgiImportedPrivate

The module is needed for compilation. The module is used during runtime. Specification version 1.0 is required.

ModulesAPIImportedOfficial

The module is needed for compilation. The module is used during runtime. Specification version 7.25 is required.

UtilitiesAPIImportedOfficial

The module is needed for compilation. The module is used during runtime. Specification version 9.3 is required.

WeakListener.setAccessibleImportedUnder Development

The module is needed for compilation. The module is used during runtime. Specification version 9.3 is required.

LookupAPIImportedOfficial

The module is needed for compilation. The module is used during runtime. Specification version 8.0 is required.

Group of property interfaces
Interface NameIn/OutStabilitySpecified in What Document?
netigso.archiveExportedUnder Development

Inside of your FrameworkFactory you can use map.get("netigso.archive") to get instance of
NetigsoArchive.

Netigso-Export-PackageExportedStable

If a NetBeans module's manifest contains tag Netigso-Export-Package, then it is used as a value of Export-Package OSGi tag, when re-exporting the module as OSGi bundle.

Group of java.io.File interfaces
Interface NameIn/OutStabilitySpecified in What Document?
netigso-bundlesExportedFriend

List of registered OSGi bundles as well as mapping of their packages to individual bundles is stored in var/cache/netigso-bundles. This file works in orchestration with content of var/cache/netigso directory where the OSGi framework usually stores its own information about bundles.

The content of the cache file is private, but the location is well known (including its relation with netigso directory), so the installer can store necessary data and speed first start of the application up.

Group of branding interfaces
Interface NameIn/OutStabilitySpecified in What Document?
org.netbeans.core.netigso.FRAMEWORK_START_LEVELExportedUnder Development

One can influence the initial OSGi framework start level by rebranding the FRAMEWORK_START_LEVEL key in org/netbeans/core/netigso/Bundle.properties. By default the key is empty, which means no change to default OSGi start level of 1.

org.netbeans.core.netigso.MODULE_START_LEVELExportedUnder Development

The meaning of enabled module (a NetBeans terminology) and started bundle (an OSGi terminology) is not the same. Although in general we recommend to start all bundles that are marked as enabled, you may want to configure this. To do so, you can use various start levels and re-brand MODULE_START_LEVEL key in org/netbeans/core/netigso/Bundle.properties to specify the start level of modules that are supposed to be started. Only modules with lower or equal start level than value of this key will be started.

org.netbeans.core.netigso.DEFAULT_BUNDLE_START_LEVELExportedUnder Development

Bundles that don't provide own start level (via config/Modules/*.xml files), get no start level by default in the NetBeans Platform, however that can be changed by branding the DEFAULT_BUNDLE_START_LEVEL key in org/netbeans/core/netigso/Bundle.properties. NetBeans IDE brands it to 4.

org.netbeans.core.netigso.FIND_COVERED_PKGSExportedUnder Development

The FIND_COVERED_PKGS branding key defines method to find list of covered packages for an OSGi bundle. Currently it can be empty or findEntries, which means Netigso will use bundle.findEntries("", null, true). As that method resolves the bundle, it may not always be appropriate. In such case brand this token to empty string and only "Export-Package" values will be used. Since version 1.23 there is also a chance to set the token to exportedIfPresent which will use the value of "Export-Package" tag when it is present, but when there is none, bundle.findEntries("", null, true) will be used.

Group of systemproperty interfaces
Interface NameIn/OutStabilitySpecified in What Document?
felix_org.osgi.frameworkExportedUnder Development

System.getProperties() that start with prefix felix. or org.osgi.framework. are read on initialization of the Netigso system and injected into configuration of OSGi container before it starts.


General Information


Project and platform dependencies


Deployment


Compatibility with environment


Access to resources


Lookup of components


Execution Environment


Format of files and protocols


Performance and Scalability


Built on October 23 2017.  |  Portions Copyright 1997-2017 Oracle. All rights reserved.