You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Mark Nuttall (JIRA)" <ji...@apache.org> on 2010/10/14 16:22:38 UTC

[jira] Resolved: (ARIES-384) ApplicationRepository should not use resolver to find the bundleInfo contained within itself

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

Mark Nuttall resolved ARIES-384.
--------------------------------

    Resolution: Fixed

Resolved. 

> ApplicationRepository should not use resolver to find the bundleInfo contained within itself
> --------------------------------------------------------------------------------------------
>
>                 Key: ARIES-384
>                 URL: https://issues.apache.org/jira/browse/ARIES-384
>             Project: Aries
>          Issue Type: Bug
>          Components: Application
>            Reporter: Emily Jiang
>            Assignee: Mark Nuttall
>         Attachments: application-management.diff
>
>
> Currently, the ApplicationRepository uses the resolver to find the by value bundles. This is incorrect, as the repository xml describing by-value bundles was not known by the repository admin, because the repository xml was passed to resolver directly instead of going through repository admin. When trying to use resolver.getBundleInfo, it will search the bundle from repository admin's known repositories. Therefore, it will never get it. The fix for this is searching bundleInfo from AriesApplication's get bundleInfo, which makes more sense for the application repository.
> The reason that the current test passed is that the no-op resolver's getBundleInfo was manupliated and return the byvalue bundles, which is not the case for the real obr resolver.
> I will also use this bug to fix the potential NPE cases.

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