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 2009/09/21 14:38:25 UTC

[jira] Commented: (FELIX-1625) Refactor bundle cache to simplify management

    [ https://issues.apache.org/jira/browse/FELIX-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757879#action_12757879 ] 

Richard S. Hall commented on FELIX-1625:
----------------------------------------

I committed a patch for this. Currently, this breaks the feature we added to allow you to pass in a BundleCache instance, since the BundleCache is now only static methods. We will have to investigate an alternative approach for replacing the cache or if it is even necessary. I will leave this issue open for now as a result.

> Refactor bundle cache to simplify management
> --------------------------------------------
>
>                 Key: FELIX-1625
>                 URL: https://issues.apache.org/jira/browse/FELIX-1625
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: felix-2.0.0
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: felix-2.2.0
>
>
> Currently, bundle cache management is a little clumsy since it spreads responsibility for managing the class across different layers. Also, it is not as efficient as it could be, since it opens the JAR file for each bundle twice when starting up. We should refactor the bundle cache to try to consolidate its management as much as possible. Since bundles already hold a reference to their archive, we don't actually need a separate bundle cache object to do this. Instead, we should try to make the operations on bundle responsible for cache management.

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