felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4525) Refactor the Framework to use the Resolver module
Date Mon, 30 Jun 2014 13:37:24 GMT

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

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

The biggest issue I had when I looked at this is I couldn't decide what was the best way to
organize my generic data structures since the framework needs impl-specific classes, but the
resolver doesn't. I guess my generics-fu just wasn't good enough at the time. Other than that
issue, the APIs are pretty similar. The only part that doesn't fit is dynamic imports, but
I did have an idea for that...

> Refactor the Framework to use the Resolver module
> -------------------------------------------------
>
>                 Key: FELIX-4525
>                 URL: https://issues.apache.org/jira/browse/FELIX-4525
>             Project: Felix
>          Issue Type: Task
>          Components: Framework
>    Affects Versions: framework-4.4.0
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>
> Currently both the framework has a resolver implementation as well as the resolver module,
which has a separate resolver implementation. The resolver module originates from the framework,
but they are not the same any more.
> It would be good to refactor the framework to use the resolver implementation from the
resolver module so that there is no code duplication any more.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message