[
https://issues.apache.org/jira/browse/FELIX-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-166.
---------------------------------
> iPOJO New Version
> -----------------
>
> Key: FELIX-166
> URL: https://issues.apache.org/jira/browse/FELIX-166
> Project: Felix
> Issue Type: New Feature
> Components: iPOJO
> Reporter: Clement Escoffier
> Assigned To: Richard S. Hall
> Attachments: patch_07_ipojo-4.txt, patch_07_metadata.txt,
> patch_07_plugin.txt
>
>
> The new version of iPOJO contains several changes :
> - Differentiation between component and component instances
> Now, the declaration of a component does not create a component instance, you
> need to add an instance tag with your component instance configuration:
> - Factory
> iPOJO 0.7.0-SNAPSHOT provides a factory systems. Indeed, for each declared
> component type, iPOJO could expose an iPOJO factory service and a
> ManagedServiceFactory service. These two services allow the creation of
> component instance dynamically. It is possible to configure these component
> instances. Moreover the given configuration can contain "complex" object like
> Map....
> - Configuration Handler
> The configuration handler was re-implemented to be more consistent with the
> OSGi specification. Moreover, the metadata, to configure the handler,
> changes. Henceforth, the metadata looks like:
> <properties configurable="true">
> <property name="int" field="foo"/>
> <property name="int" field="bar"/>
> </properties>
> The configurable attribute allows the publication of the "ManagedService"
> service (dynamic reconfiguration of the component instance)
> - Performance improvement :
> The iPOJO core was patched to avoid useless handler indirection.
> - Filtered service dependency :
> The dependency handler had bugs when managing dependency with a filter. This
> bug was corrected. Now, the dynamism of filtered dependency works.
> - Import / Export of the "org.osgi.service.cm" package :
> The previous version of iPOJO does not export correctly the package (bad
> version number).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
