You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Holly Cummins (JIRA)" <ji...@apache.org> on 2011/01/15 13:55:45 UTC
[jira] Created: (ARIES-542) Use of PlatformRepository in resolvers
needs to be more flexible
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.
[jira] Resolved: (ARIES-542) Use of PlatformRepository in resolvers
needs to be more flexible
Posted by "Holly Cummins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Holly Cummins resolved ARIES-542.
---------------------------------
Resolution: Fixed
Further APIs now added
> 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.
[jira] Resolved: (ARIES-542) Use of PlatformRepository in resolvers
needs to be more flexible
Posted by "Holly Cummins (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Reopened: (ARIES-542) Use of PlatformRepository in resolvers
needs to be more flexible
Posted by "Holly Cummins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Holly Cummins reopened ARIES-542:
---------------------------------
Re-opening since I missed the DeploymentManifestManager interface in my initial changes.
> 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.