mbs.bundles.cacheHeaders

–

A list of comma-separated manifest headers, which the framework will keep in its cache for faster checking if a bundle has a specific header through the Framework Access service. This property should not contain more than 32 headers.

mbs.bundles.getStateSimple

true

If this property is false, when called the Bundle's getState method will try to resolve the relevant bundle.

mbs.bundles.defaultFragAttach

always

Specifies the default policy for fragment attachment in case the host bundle does not contain the fragment-attachment directive within the Bundle-SymbolicName manifest header. Possible values are taken from the OSGi Framework Specification, in particular always, resolve-time and never.

mbs.bundles.noStrictR4

false

If true, the framework will take into account the OSGi R4-specific manifest headers (Bundle-SymbolicName, Fragment-Host, etc.) without requiring from bundles to have the Bundle-ManifestVersion: 2 manifest header.

mbs.loader.type

–

The type of bundle loaders to use for a specific platform. If this property is not set, a default type will be used. The property can have the following value of custom – for a custom bundle loader. It allows working with a custom implementation of com.prosyst.mbs.framework.classloader.ClassProvider.

mbs.loader.class

com.prosyst.mbs.impl.framework.DefaultClassProvider

The bundle loader class, implementing

com.prosyst.mbs.framework.classloader.ClassProvider,

that will be used for loading bundle classes. The property takes effect only if mbs.loader.type is set to custom.

mbs.loader.setsigners

true

If true, on defining a new bundle class the setSigners method of the corresponding bundle loader will be called. This property is recommended to be true for JDK1.1.

mbs.manifest.osname.ignoreSpaces

true

When true, the framework ignores the spaces in the os.name system property value, used for loading bundle native libraries appropriate for the runtime environment. For example, "windows 2000" will be considered as "windows2000".

mbs.update

eager

Specifies the update mode of the framework. The property can be eager or lazy. The property can be changed at runtime and the change will have effect the next time a bundle is uninstalled or updated.

mbs.customFrameworkLoader

false

If true, the framework will use a special class loader, called the Framework Loader, for managing the framework in case an extension bundle is installed.

mbs.noFwRestart

false

If true, the framework process will not be restarted when a boot class path extension bundle is installed or updated.

mbs.core.timeout

30000

Provides the time-out in milliseconds for a bundle to start or stop.

mbs.disableContextClassLoader

false

By default, to avoid some class loading problems, the framework sets the context class loader of its current thread to the class loader of the bundle that it currently calls back (it calls the bundle's start/stop activator method, gets a bundle's factory service, etc.). Set this property to false, to have the class loader of the framework used in its current thread.

mbs.loader.checkForArrayName

false

If true, the framework will not use ClassLoader.loadClass() for array classes but will invoke Class.forName().

mbs.fm.faultsInStartup

false

If true and the Fault Manager is available, the framework will signal faults when specific bundles fail to load or cannot be started.

mbs.bundles.lazy

true

If true, the lazy initialization feature will be on.