mbs.measurements.full

boolean

false

Enables generation of information about the startup time of different functional parts of the Metatype Bundle.

mbs.measurements.bundles

boolean

mbs.metadata.cache

boolean

false

Enables caching of XML-formatted metatypes.

mbs.metadata.configs.process

boolean

false

Turns on processing of metatypes associated with bundle configurations and factory configurations by the Metadata Manager itself. This property should be set to true in case there is no associated Metadata Plugin such as the Configuration Admin.

mbs.metadata.configs.store

boolean

false

If processing of configuration metadata is on, enables storage of configuration metadata.

mbs.metatype.lazyInit

boolean

false

Defines whether the Metatype bundle should be started in a lazy initialization mode (when true) or not (when false).

mbs.mtp.initOnResolve

boolean

false

If true, the Metadata Manager will process metatypes of newly-installed bundles upon their resolving instead of upon installation.

mbs.metatype.storeDBinDataRootDir

boolean

false

If true, the Metatype Bundle will place its persistent database into the root directory of its storage area instead of in the storage of the Core Database Bundle. Then, upon uninstalling the Metatype Bundle, its persistent data will be deleted as well.

mbs.mtp.externalDir

String

../../../configs

If you need to have easy access to the configuration metatype XML file of a specific bundle in order to edit its properties quickly, use this property to specify the path to a directory outside the bundle JAR file which contains the metadata. The path should be relative to bin/vms/<vm_name> or should be absolute.

Each XML file must be named as <pid>.xml or <fpid>.xml in accordance with the associated configuration Managed Service or Managed Service Factory.

By default, the Metatype Bundle will look in the configs directory of the OSGi runtime.

Presently, this property is valid only for metatype XML files following the Metatype Extension format.

mbs.mtp.removeTypeTimeout

int

15000

Specifies the timeout in milliseconds for keeping metatype information for a plugin that has been unregistered, in case the plugin is registered before the end of the timeout. Value of -1 implies no limit for storing metatype information for a plugin in the database.

mbs.metatype.scanMetaDataDir

boolean

true

When set to false disables scanning the external metadata directory for xml files with newer metadata version. Otherwise by default such a check is made once on every framework restart.