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 (Created) (JIRA)" <ji...@apache.org> on 2011/09/30 19:35:45 UTC

[jira] [Created] (FELIX-3141) [Framework] Framework should filter removal pending fragments not the resolver

[Framework] Framework should filter removal pending fragments not the resolver
------------------------------------------------------------------------------

                 Key: FELIX-3141
                 URL: https://issues.apache.org/jira/browse/FELIX-3141
             Project: Felix
          Issue Type: Improvement
          Components: Framework
    Affects Versions: framework-4.0.0
            Reporter: Richard S. Hall
            Assignee: Richard S. Hall
            Priority: Minor
             Fix For: framework-4.0.1


Currently, the resolver implementation filters out fragment bundle revisions that are removal pending (i.e., have been updated or uninstalled, but not refreshed). This should actually be the responsibility of the framework, since technically they are invalid revisions and the resolver really doesn't have a way to determine this without looking at bundles since it operates on revisions. Effectively, this causes it to cross too many abstraction layers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (FELIX-3141) [Framework] Framework should filter removal pending fragments not the resolver

Posted by "Richard S. Hall (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard S. Hall closed FELIX-3141.
----------------------------------

    Resolution: Fixed

Committed a patch.
                
> [Framework] Framework should filter removal pending fragments not the resolver
> ------------------------------------------------------------------------------
>
>                 Key: FELIX-3141
>                 URL: https://issues.apache.org/jira/browse/FELIX-3141
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: framework-4.0.0
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>            Priority: Minor
>             Fix For: framework-4.0.1
>
>
> Currently, the resolver implementation filters out fragment bundle revisions that are removal pending (i.e., have been updated or uninstalled, but not refreshed). This should actually be the responsibility of the framework, since technically they are invalid revisions and the resolver really doesn't have a way to determine this without looking at bundles since it operates on revisions. Effectively, this causes it to cross too many abstraction layers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira