felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clement Escoffier (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (FELIX-683) Supporting lists and vectors in the service dependency management
Date Sun, 17 Aug 2008 16:35:44 GMT

     [ https://issues.apache.org/jira/browse/FELIX-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Clement Escoffier resolved FELIX-683.
-------------------------------------

    Resolution: Fixed

Fixed in the revision 686620
Now iPOJO supports list and vector injection for service objects. So, it is possible for a
pojo to access services through a field of the type list or vector. Be aware, that these fields
do not contribute to service interface detection. So, the required service interface must
either be mentioned in the component metadata (interface attribute) or be "discoverable" by
using bind/unbind callbacks (with a service object argument).

> Supporting lists and vectors in the service dependency management
> -----------------------------------------------------------------
>
>                 Key: FELIX-683
>                 URL: https://issues.apache.org/jira/browse/FELIX-683
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>    Affects Versions: iPOJO-0.8.0
>            Reporter: Clement Escoffier
>            Assignee: Clement Escoffier
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> iPOJO does not yet support the injection of list and vector (containing service object)
when the service dependency is aggregate. Indeed, only arrays are supported. The purpose of
this improvement is to provide this support. Then, it should be possible for the pojo to get
service objects from a list or a vector field. The only limitation of this support is the
service specification detection. iPOJO will not be able to automatically detect the required
service type (i.e. interface) for a dependency injected inside a list or a vector as the type
is not contained in the field declaration. So, this force the developer to specify the service
interface in the metadata ('interface' attribute), or to attach bind/unbind method receiving
a service object. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message