aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Holly Cummins (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ARIES-542) Use of PlatformRepository in resolvers needs to be more flexible
Date Sat, 15 Jan 2011 13:01:47 GMT

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

Holly Cummins resolved ARIES-542.
---------------------------------

    Resolution: Fixed

Changes now delivered.

> Use of PlatformRepository in resolvers needs to be more flexible
> ----------------------------------------------------------------
>
>                 Key: ARIES-542
>                 URL: https://issues.apache.org/jira/browse/ARIES-542
>             Project: Aries
>          Issue Type: Improvement
>          Components: Application
>    Affects Versions: 0.3
>            Reporter: Holly Cummins
>            Assignee: Holly Cummins
>            Priority: Minor
>             Fix For: 0.3
>
>
> When resolving, Aries has the notion of a local repository, which represents the OSGi
framework, and a platform repository, which would usually represent the bundles provided by
higher level infrastructure, like an application server. At the moment the platform repository
is provided by a blueprint-injected service, which works very cleanly if there's only one
platform to be resolved against, but less well otherwise. 
> We need to add a new method to AriesApplicationResolver which takes in a platform repository
and uses it for resolution as an override to the service. (The alternative is to rapidly register
and unregister services between calls to the platform repository, which is both awkward and
prone to timing failures.)

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


Mime
View raw message