Pax ConfMan - Scanner - Registry

Scans OSGi Service Registry for configurations. Basically any service can be considered for a configuration if it matches the specified filter (see bellow). But to be usable as a configuration there should be an [adaptor] that is able to convert it to a configuration dictionary. Registry scanner is implemented having the whiteboard pattern in mind. So, to configure a target service you should just register a service that has the following associated properties:

• target.service.pid — this is a mandatory property as it denotes he configuration pid
• target.service.factoryPid — factory pid. If this is set the configuration is considered to be a factory configuration.
• target.service.factoryInstance — factory instance. A factory configuration can have more instances.
• target.service.location — bundle location. This is an optional property and has the meaning of binding the configuration to a specified location.

The registered service can be any type of object (see remark about adaptors above) as for example a Dictionary (and implementation classes as Hashtable or Properties), can be a File or even an InputStream. And as adaptors are plug-able you can write you custom one.

Filter

Registry scanner tracks services registered within OSGi Service Registry for those services that matches the configured filter. By default it tracks services that have an associated property named target.service.pid or target.service.factoryPid + target.service.factoryInstance (matches filter "(&(target.service.pid=*)(&(target.service.factoryPid=*)(target.service.factoryInstance=*)))".

Configuration

Issue tracker

Issues, bugs, and feature requests can be submitted to the issue tracking system.