You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2017/04/19 23:21:04 UTC
[jira] [Updated] (FELIX-5572) Reference target filter fails when
using field strategy for multiple cardinality reference with multiple
component instances
[ https://issues.apache.org/jira/browse/FELIX-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated FELIX-5572:
------------------------------------
Fix Version/s: (was: scr-2.1.0)
scr-2.0.10
> Reference target filter fails when using field strategy for multiple cardinality reference with multiple component instances
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-5572
> URL: https://issues.apache.org/jira/browse/FELIX-5572
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-2.0.8
> Reporter: Karel Haeck
> Assignee: Carsten Ziegeler
> Fix For: scr-2.0.10
>
>
> In this case the injected list seems additive, that is it contains all the references matched for previous component instances,
> as well as the one matched by the current component. As such the list contains references that do not match the target filter.
> A typical example is a Route component referencing Destinations (where Route and Destination are both DS components).
> Using configuration admin each instance of the route has its own destinations.target filter, but the injected list does not match the filter.
> When using method strategy, the target filter works as expected. Note also that the DS introspection API reports the correct
> references, but the actual injected list does not match the introspection API.
> See https://github.com/Amplifino/snippets for a bndtools workspace example. ( branch workaround contains the method strategy workaround).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)