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-860) Temporal Dependency Proxy injection
Date Mon, 19 Jan 2009 09:02:02 GMT

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

Clement Escoffier resolved FELIX-860.

    Resolution: Fixed

Fix at r735632
- Dynamic proxies were replaced by ASM proxies (more efficient).
- Non-proxied injection use a ThreadLocal mechanism to assert consistency (quiescence).

> Temporal Dependency Proxy injection
> -----------------------------------
>                 Key: FELIX-860
>                 URL: https://issues.apache.org/jira/browse/FELIX-860
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>    Affects Versions: iPOJO-1.0.0
>            Reporter: Clement Escoffier
>            Assignee: Clement Escoffier
>             Fix For: iPOJO-1.2.0
> iPOJO Temporal dependencies injects directly the service object(s).
> To be able to given service objects to collaborators (helper objects) without breaking
the dynamism, proxies could also be injected.
> In this case, it's no more a direct reference on service object(s) but a reference on
a proxy wrapping the dependency.
> For scalar dependency an injected 'dynamic' proxy can delegate to service provider, managing
on timeout policies during the lookup.
> For aggregate dependencies, a collection can be injected. When the code call the iterator()
or the toArray(...) methods service objects are returned (a cached copy). The timeout policy
can also be applied during the service lookup.
> So, with those proxied access, temporal dependencies can be given to helper components

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

View raw message