...
Property | Default Value | Description |
---|---|---|
| 1 | Defines a logging level at which messages are logged. This configuration property is converted to an
|
| — | sets the log level to |
| — | Disables logging completely if set to |
| | Enables Component Factory functionality not compliant with the Declarative Services 1.1 specification if set to |
| | Enables workaround functionality to pass the OSGi CT. Generally this property should not be set to |
| | Whether or not to keep instances of delayed components once they are not referred to any more. The Declarative Services specifications suggests that instances of delayed components are disposed off if there is not used any longer. Setting this flag causes the components to not be disposed off and thus prevent them from being constantly recreated if often used. Examples of such components may be EventHandler services. The default is to dispose off unused components. See FELIX-3039 for details. |
This configuration mechanism is implemented in the ScrConfiguration and its helper classes.
...
Note |
---|
If you don't know what this section is about, just ignore it and leave the |
Versions of the Apache Felix Declarative Services implementation prior to 1.2.0 supported handling of Component Factory components which is not specification compliant.
...
If you know that you are using Component Factory components depending on this non-standard behaviour you may set the ds.factory.enabled
configuration property to true
(the default of this property is false
thus disabling this functionality for specification compliance).
For details also refer to FELIX-1416
Administration
The OSGi Compendium specification defines no administrative API for Declarative Services. As of version 0.9.0-20071123.131249-8 a simple administrative API is provided the Apache Felix implementation. The bundle itself also has a Felix Shell Command providing easy commands to introspect the states of the registered components.
...