Package org.apache.felix.dm
Interface Component
- All Known Subinterfaces:
AdapterComponent,AspectComponent,BundleComponent,ComponentContext,FactoryComponent,ResourceComponent
@ProviderType
public interface Component
Component interface. Components are the main building blocks for OSGi applications.
They can publish themselves as a service, and they can have dependencies. These
dependencies will influence their life cycle as component will only be activated
when all required dependencies are available.
- Author:
- Felix Project Team
-
Nested Class Summary
Nested Classes -
Method Summary
Modifier and TypeMethodDescriptionadd(ComponentStateListener listener) Adds a component state listener to this component.add(Dependency... dependencies) Adds dependency(ies) to this component, atomically.Returns the component description (dependencies, service provided, etc ...).Returns the dependency manager associated with this component.<U> UReturns the instance that make up this component.Object[]Returns the composition instances that make up this component, or just the component instance if it does not have a composition, or an empty array if the component has not even been instantiated.<K,V> Dictionary <K, V> Returns the component service properties.org.osgi.framework.ServiceRegistrationReturns the service registration for this component.remove(ComponentStateListener listener) Removes a component state listener from this component.remove(Dependency d) Removes a dependency from the component.setAutoConfig(Class<?> clazz, boolean autoConfig) Configures auto configuration of injected classes in the component instance.setAutoConfig(Class<?> clazz, String instanceName) Configures auto configuration of injected classes in the component instance.Sets the names of the methods used as callbacks.setCallbacks(String init, String start, String stop, String destroy) Sets the names of the methods used as callbacks.setComposition(Object instance, String getMethod) Sets the instance and method to invoke to get back all instances that are part of a composition and need dependencies injected.setComposition(String getMethod) Sets the method to invoke on the service implementation to get back all instances that are part of a composition and need dependencies injected.Activate debug for this component.setFactory(Object factory, String createMethod) Sets the factory to use to create the implementation.setFactory(String createMethod) Sets the factory to use to create the implementation.setImplementation(Object implementation) Sets the implementation for this component.setInterface(Class<?>[] serviceNames, Dictionary<?, ?> properties) Sets the public interfaces under which this component should be registered in the OSGi service registry.setInterface(Class<?> serviceName, Dictionary<?, ?> properties) Sets the public interface under which this component should be registered in the OSGi service registry.setInterface(String[] serviceNames, Dictionary<?, ?> properties) Sets the public interfaces under which this component should be registered in the OSGi service registry.setInterface(String serviceName, Dictionary<?, ?> properties) Sets the public interface under which this component should be registered in the OSGi service registry.setScope(Component.ServiceScope scope) Sets the component scope.setServiceProperties(Dictionary<?, ?> serviceProperties) Sets the service properties associated with the component.
-
Method Details
-
setScope
Sets the component scope.- Parameters:
scope- the component scope (default=SINGLETON)- Returns:
- this component
-
setImplementation
Sets the implementation for this component. You can actually specify an instance you have instantiated manually, or aClassthat will be instantiated using its default constructor when the required dependencies are resolved, effectively giving you a lazy instantiation mechanism. There are four special methods that are called when found through reflection to give you life cycle management options:init()is invoked after the instance has been created and dependencies have been resolved, and can be used to initialize the internal state of the instance or even to add more dependencies based on runtime statestart()is invoked right before the service is registeredstop()is invoked right after the service is unregistereddestroy()is invoked after all dependencies are removed
- Parameters:
implementation- the implementation- Returns:
- this component
- See Also:
-
add
Adds dependency(ies) to this component, atomically. If the component is already active or if you add dependencies from the init method, then you should add all the dependencies in one single add method call (using the varargs argument), because this method may trigger component activation (like the ServiceTracker.open() method does).- Parameters:
dependencies- the dependencies to add.- Returns:
- this component
-
remove
Removes a dependency from the component.- Parameters:
d- the dependency to remove- Returns:
- this component
-
add
Adds a component state listener to this component.- Parameters:
listener- the state listener
-
remove
Removes a component state listener from this component.- Parameters:
listener- the state listener
-
setInterface
Sets the public interface under which this component should be registered in the OSGi service registry.- Parameters:
serviceName- the name of the service interfaceproperties- the properties for this service- Returns:
- this component
-
setInterface
Sets the public interfaces under which this component should be registered in the OSGi service registry.- Parameters:
serviceNames- the names of the service interfaceproperties- the properties for these services- Returns:
- this component
-
setInterface
Sets the public interface under which this component should be registered in the OSGi service registry.- Parameters:
serviceName- the name of the service interfaceproperties- the properties for this service- Returns:
- this component
-
setInterface
Sets the public interfaces under which this component should be registered in the OSGi service registry.- Parameters:
serviceNames- the names of the service interfaceproperties- the properties for these services- Returns:
- this component
-
setAutoConfig
Configures auto configuration of injected classes in the component instance. The following injections are currently performed, unless you explicitly turn them off:- BundleContext
- the bundle context of the bundle
- ServiceRegistration
- the service registration used to register your service
- DependencyManager
- the dependency manager instance
- Component
- the component instance of the dependency manager
- Parameters:
clazz- the class (from the list above)autoConfig-falseto turn off auto configuration
-
setAutoConfig
Configures auto configuration of injected classes in the component instance.- Parameters:
clazz- the class (from the list above)instanceName- the name of the instance to inject the class into- See Also:
-
setServiceProperties
Sets the service properties associated with the component. If the service was already registered, it will be updated.- Parameters:
serviceProperties- the properties
-
setCallbacks
Sets the names of the methods used as callbacks. These methods, when found, are invoked as part of the life cycle management of the component implementation. The dependency manager will look for a method of this name with the following signatures, in this order:- method(Component component)
- method()
- Parameters:
init- the name of the init methodstart- the name of the start methodstop- the name of the stop methoddestroy- the name of the destroy method- Returns:
- the component
-
setCallbacks
Sets the names of the methods used as callbacks. These methods, when found, are invoked on the specified instance as part of the life cycle management of the component implementation.See setCallbacks(String init, String start, String stop, String destroy) for more information on the signatures. Specifying an instance means you can create a manager that will be invoked whenever the life cycle of a component changes and this manager can then decide how to expose this life cycle to the actual component, offering an important indirection when developing your own component models.
- Returns:
- this component
-
setFactory
Sets the factory to use to create the implementation. You can specify both the factory class and method to invoke. The method should return the implementation, and can use any method to create it. Actually, this can be used together withsetCompositionto create a composition of instances that work together to implement a component. The factory itself can also be instantiated lazily by not specifying an instance, but aClass.- Parameters:
factory- the factory instance or classcreateMethod- the name of the create method- Returns:
- this component
-
setFactory
Sets the factory to use to create the implementation. You specify the method to invoke. The method should return the implementation, and can use any method to create it. Actually, this can be used together withsetCompositionto create a composition of instances that work together to implement a component.Note that currently, there is no default for the factory, so please use
setFactory(factory, createMethod)instead.- Parameters:
createMethod- the name of the create method- Returns:
- this component
-
setComposition
Sets the instance and method to invoke to get back all instances that are part of a composition and need dependencies injected. All of them will be searched for any of the dependencies. The method that is invoked must return anObject[].- Parameters:
instance- the instance that has the methodgetMethod- the method to invoke- Returns:
- this component
-
setComposition
Sets the method to invoke on the service implementation to get back all instances that are part of a composition and need dependencies injected. All of them will be searched for any of the dependencies. The method that is invoked must return anObject[].- Parameters:
getMethod- the method to invoke- Returns:
- this component
-
setDebug
Activate debug for this component. Informations related to dependency processing will be displayed using osgi log service, our to standard output if no log service is currently available.- Parameters:
label-
-
getServiceRegistration
org.osgi.framework.ServiceRegistration getServiceRegistration()Returns the service registration for this component. The method will returnnullif no service registration is available, for example if this component is not registered as a service at all.- Returns:
- the service registration
-
getInstance
<U> U getInstance()Returns the instance that make up this component. If the component has a composition of instances, then the first instance of the composition is returned. Null is returned if the component has not even been instantiated.- Returns:
- the component instances
-
getInstances
Object[] getInstances()Returns the composition instances that make up this component, or just the component instance if it does not have a composition, or an empty array if the component has not even been instantiated.- Returns:
- the component instances
-
getServiceProperties
Returns the component service properties. The returned dictionary is either empty if no service properties were defined for this component, or copy of the existing service properties associated with this component.- Returns:
- a copy of the service properties associated to this component or an empty dictionary if no service properties were defined for this component.
-
getDependencyManager
DependencyManager getDependencyManager()Returns the dependency manager associated with this component.- Returns:
- the dependency manager associated with this component.
-
getComponentDeclaration
ComponentDeclaration getComponentDeclaration()Returns the component description (dependencies, service provided, etc ...).- Returns:
- the component description (dependencies, service provided, etc ...).
-