You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2011/03/11 16:13:59 UTC

[jira] Updated: (FELIX-2859) [Framework] Modify resolver to be self-contained with respect to singleton handling

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

Richard S. Hall updated FELIX-2859:
-----------------------------------

    Fix Version/s:     (was: framework-4.0.0)
                   framework-3.2.0

> [Framework] Modify resolver to be self-contained with respect to singleton handling
> -----------------------------------------------------------------------------------
>
>                 Key: FELIX-2859
>                 URL: https://issues.apache.org/jira/browse/FELIX-2859
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: framework-3.0.9
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: framework-3.2.0
>
>
> Currently, the resolver does not handle singletons or even know about them at all. The resolver state, which is an external entity handles this. This approach limits reuse of the resolver since it is not self-contained. The resolver should be modified so that it directly processes singletons. To do this, it will have to determine which, if any, singletons are involved in a given resolve and limit their inclusion appropriately. This is similar to what currently happens in the resolver state. The main difference is that the resolver state does this at bundle install time, which is more efficient. A self-contained resolver will have to do it every time there is a resolve involving singletons, so it might be less efficient.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira