iPOJO Factories Principles
iPOJO defines a factory for each declared component type. These factories are used to create component instances. This document presents how to declare instances inside iPOJO metadata, and how-to create, dispose and reconfigure dynamically instances.
Note: This page refers on iPOJO 0.8.0 and iPOJO 0.9.0-SNAPSHOT features.
Preliminary Concepts
Component Type
A component type is a kind of instance template. If we compare component concepts with object oriented programming, component types are classes and component instances are objects. A component type is declared inside a metadata file (generally named 'metadata.xml'). The next snippet shows you a component type declaration:
<component className="..." name="MyFactory">
...
...
</component>
A component type declaration begins generally by '<component>' and is composed by:
- An implementation class ('className', mandatory)
- A name ('name')
- Handler configuration (see handler guide)
The 'name' attribute contains the factory name. If not specified, the 'className' attribute is used as the factory name. This factory name is used to refer to the factory (and consequently to the component type).
A factory can be public or private. A public factory allows creating instances dynamically and from other bundles. A private factory can only be used to create instances declared in the same metadata than the component type (i.e. in the same bundle). By default, factories are public. To set the factory to private add the 'public="false"'' attribute in the '<component>' element, such as:
<component className="..." name="MyPrivateFactory" public="false">
...
...
</component>
Public factories offer different way to create instances:
- Instances can be declared in iPOJO descriptor in any bundle
- Instances can be created dynamically by using the API
Indeed, iPOJO will publish two services to access to the factory through the API:
- org.apache.felix.ipojo.Factory : iPOJO Factory Interface
- org.osgi.service.cm.ManagedServiceFactory : Config Admin Interface
The factory name will be used a service.pid property for these services. The service.pid is unique and persists between framework restarts. The service.pid of the factory equals the factory name.
Factories are either valid or invalid. You can't create instances until a factory becomes valid. A factory is invalid if required handlers are missing. This issue occurs only if the component type uses external handlers.
Component Instance
A component instance is an instance of a component type. For example, if a component type declares providing and requiring services, the component instances, will expose and require really those services. Several instances can be created from one factory, but all these instances will be managed as different entities, and so are independent. A component instance is characterized by:
- a component type (the factory name)
- an instance name (used to identify the instance, is unique)
- a configuration : a set of <key, value> couple
A factory keeps a reference on each created instances. If the factory stops, goes away, or becomes invalid, all created instances are stopped and are destroyed.
To create an instance, the instance must refer to the factory (by using the factory name), and provide the instance configuration. This configuration can specify the instance name ('instance.name' property). Be aware that this name must be unique. If not specified, iPOJO will generate a unique name.
A factory can refuse the creation if the configuration is not acceptable or if the factory is invalid. An unacceptable configuration is a not suitable configuration in regard to component type. Reasons for unacceptable configuration are:
- The instance name is not set or not unique
- A property required by the component type is missing inside the configuration
- A pushed property has a wrong type
How-to declare instances inside metadata files
The main way to create instances is to declare those instances inside the iPOJO descriptor file (i.e. 'metadata.xml'). Those declarations can use either public factories from any bundle, or private factories from the same bundle. Private factories are generally used to guaranty singleton instance as instances can only be created inside the same bundle.
When a instance declaration targets an external public factory, it will wait until the factory becomes available. So, the instance will be created only when the factory appears and is valid. If the factory disappears after the instance creation, the instance is disposed and will be recreated as soon as the factory comes back.
The next snippet shows how to declare an instance in the metadata:
<instance component="component factory name" name = "instance name" >
<property name="a property name" value="a string form of the value"/>
<property name="another prop name" value="the string form value "/>
</instance>
An instance declaration must contain the 'component' attribute. This attribute specifies the factory name (i.e. the component type). It can use either the factory name or the class name. The 'name' attribute allows setting the instance name. If not set, iPOJO will generate a unique name for you. Then, instances can declare properties. Those property are mostly key-value pair. The key refer to a property name from the component type declaration such as in:
<component className="..." name="my-factory">
<properties>
<property name="foo" field="m_foo"/>
</properties>
</component>
<instance component="my-factory ">
<property name="foo" value="bla bla bla"/>
</instance>
The string-form of the property value will be use to create the real object at runtime. If an unacceptable configuration is set, the instance is not created, and an error message appears to the console (and in the Log Service if present).
Instance declaration properties can be more complex than only 'key-value'. It can contains structure like list, map, dictionary and arrays such as in:
<instance component="a.factory" name="complex-props">
<property name="array" type="array">
<property value="a"/>
<property value="b"/>
</property>
<property name="list" type="list">
<property value="a"/>
<property value="b"/>
</property>
<property name="dict" type="dictionary">
<property name="a" value="a"/>
<property name="b" value="b"/>
</property>
<property name="map" type="map">
<property name="a" value="a"/>
<property name="b" value="b"/>
</property>
<property name="complex-array" type="array">
<property type="list">
<property value="a"/>
<property value="b"/>
</property>
<property type="list">
<property value="c"/>
<property value="d"/>
</property>
</property>
<property name="empty-array" type="array"/>
<property name="empty-list" type="list"/>
<property name="empty-map" type="map"/>
</instance>
Note: The 'instance.name' and 'factory.name' property should not be set directly. iPOJO will manage those properties. The 'instance.name' is created from the 'name' attribute of the instance declaration.
Creating, disposing and reconfiguring instances with the API
A public factory is accessible through an exposed service (org.apache.felix.ipojo.Factory ![]() . This service is accessible as any other OSGi service, and could be an iPOJO dependency using a LDAP filter or the 'from' attribute such as in:
<component classname="...">
<requires field="a_field" filter="(factory.name=factory-name)"/>
<requires field="another_field" from="another-factory"/>
</component>
Creating instances
Once you have a reference on the factory you can create instance with the 'createComponentInstance' method.
ComponentInstance createComponentInstance(java.util.Dictionary configuration)
throws UnacceptableConfiguration,
MissingHandlerException,
ConfigurationException
This method returns a reference on the created instance. As you see, the method receives a dictionary containing the instance configuration. This configuration contains key-value pairs. However, values are either object (of the adequate type) of String used to create objects. This configuration can be 'null' if no properties have to be pushed.
Note: The 'instance.name' property can be used to specify the instance name.
Instances are automatically started when created. However, the instance can be invalid, if at least one handler is not valid).
The instance creation process can fail. Three exceptions can be thrown during the creation:
- UnacceptableConfiguration means that mandatory properties are missing in the instance configuration
- MissingHandlerException means that the factory is not valid (i.e. an external handler is missing)
- ConfigurationException means that the instance configuration has failed. The cause can be either an issue in the component type description or an invalid property type.
If an error occurs, a comprehensive message is reported in order to solve the issue.
The next snippet shows an example of instance creation:
Properties props = new Properties();
props.put("instance.name","instance-name");
props.put("foo", "blablabla");
try {
instance = fact.createComponentInstance(props);
} catch(Exception e) {
fail("Cannot create the instance : " + e.getMessage());
}
Disposing created instance
You can only disposed instances that you created. To dispose an instance, just call the 'dispose' method on the ComponentInstance object (returned by the createComponentInstance method).
Reconfiguring instance
To reconfigure an instance, call the 'reconfigure' method on the ComponentInstance object. This method receives the new set of properties. Be aware that the 'instance.name' property cannot be changed.
Properties props2 = new Properties();
props2.put("foo", "abc");
instance.reconfigure(props2);
How to use the ManagedServiceFactory to create, disposed and reconfigure instances
The principle of the ManagedServiceFactory is the same as the iPOJO Factory Service. So, you can create, dispose and reconfigure instances with the Configuration Admin. For further information, read the OSGi R4 Compendium - Configuration Admin chapter.
Be aware that the 'updated' method is used both for instance creation (if the given configuration is new) and to reconfigure an existing instance. The 'deleted' method is used to dispose instances. |
