[
https://issues.apache.org/jira/browse/ARIES-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839639#action_12839639
]
Thomas Diesler commented on ARIES-177:
--------------------------------------
There is a potential problem in Framework.resolveBundles(long[]
bundleIdentifiers) when given partially invalid bundle ids
To be in sync with resolveBundle(long bundleIdentifier), we could change to
public boolean resolveBundles(long[] bundleIdentifiers) throws IOException {
Bundle[] bundles = null;
if(bundleIdentifiers != null)
{
bundles = new Bundle[bundleIdentifiers.length];
for (int i = 0; i < bundleIdentifiers.length; i++)
{
bundles[i] = FrameworkUtils.resolveBundle(context,
bundleIdentifiers[i]);
}
}
return packageAdmin.resolveBundles(bundles);
}
In the API docs he behaviour is unspecified. I raised the issue with the EEG
https://www.osgi.org/members/bugzilla/show_bug.cgi?id=1606
> JMX FrameworkMBean does not allow to resolve/refresh all bundles
> ----------------------------------------------------------------
>
> Key: ARIES-177
> URL: https://issues.apache.org/jira/browse/ARIES-177
> Project: Aries
> Issue Type: Bug
> Components: JMX
> Reporter: Thomas Diesler
> Assignee: Adam Wojtuniak
> Attachments: aries-177.patch
>
>
> The signature and API docs of
> FrameworkMBean.refreshBundles(long[] bundleIdentifiers)
> FrameworkMBean.resolveBundles(long[] bundleIdentifiers)
> does not obviously allow to resolve/refresh all bundles.
> A client would be forced to collect all ids before making the call.
> PackageAdmin however uses a null paramter to mean 'all bundles'.
> https://www.osgi.org/members/bugzilla/show_bug.cgi?id=1586
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
