Annotation Type Element and Description |
---|
org.apache.felix.dm.annotation.api.ConfigurationDependency.description
use standard bndtools metatype annotations instead (see http://www.aqute.biz/Bnd/MetaType)
|
org.apache.felix.dm.annotation.api.FactoryConfigurationAdapterService.description
use standard bndtools metatype annotations instead (see http://www.aqute.biz/Bnd/MetaType)
|
org.apache.felix.dm.annotation.api.FactoryConfigurationAdapterService.factoryPidClass
use
FactoryConfigurationAdapterService.configType() and accept a configuration type parameter from your updated callback. The pid
is then assumed to match the fqdn of the configuration type. |
org.apache.felix.dm.annotation.api.Component.factorySet
use
Component.factoryName() instead of a factorySet. |
org.apache.felix.dm.annotation.api.ConfigurationDependency.heading
use standard bndtools metatype annotations instead (see http://www.aqute.biz/Bnd/MetaType)
|
org.apache.felix.dm.annotation.api.FactoryConfigurationAdapterService.heading
use standard bndtools metatype annotations instead (see http://www.aqute.biz/Bnd/MetaType)
|
org.apache.felix.dm.annotation.api.ConfigurationDependency.metadata
use standard bndtools metatype annotations instead (see http://www.aqute.biz/Bnd/MetaType)
|
org.apache.felix.dm.annotation.api.FactoryConfigurationAdapterService.metadata
use standard bndtools metatype annotations instead (see http://www.aqute.biz/Bnd/MetaType)
|
org.apache.felix.dm.annotation.api.ConfigurationDependency.pidClass
just define an updated callback which accepts as argument a configuration type.
|
org.apache.felix.dm.annotation.api.Property.values
use
Property.value() attribute. |