You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Thomas Watson (JIRA)" <ji...@apache.org> on 2012/10/18 20:16:03 UTC

[jira] [Updated] (FELIX-3716) Improve support for cardinality multiple

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

Thomas Watson updated FELIX-3716:
---------------------------------

    Attachment: org.apache.felix.resolver.patch

A possible fix to support multiple cardinality.

This fix is more involved that I would have liked.  For multiple cardinality requirements the check for consistency will remove any candidates that cause a conflict in the class space by using  a copy of the current permutation and removing them from the copy.   If there is still at least one remaining candidate for the requirement the original permutation check continues as if there is no conflict in order to verify all the remaining requirements.  If we get to the end of the consistency check with no errors then we use the copy of the permutation where we removed all the candidates that caused conflicts for multiple cardinality requirements.

                
> Improve support for cardinality multiple
> ----------------------------------------
>
>                 Key: FELIX-3716
>                 URL: https://issues.apache.org/jira/browse/FELIX-3716
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>         Environment: All
>            Reporter: Thomas Watson
>         Attachments: org.apache.felix.resolver.patch
>
>
> The resolver implementation currently ignores the cardinality directive.  We should try to improve this to allow a requirement to get wired to multiple providers if the cardinality directive is set to multiple.
> I have been working on a fix to this but am waiting for the fix in issue 3707 to get release first so I can base the patch off that fix.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira