You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2015/01/26 12:30:34 UTC
[jira] [Resolved] (ARIES-1289) Problematic directory entry check in
ProviderBundleTrackerCustomizer
[ https://issues.apache.org/jira/browse/ARIES-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bosschaert resolved ARIES-1289.
-------------------------------------
Resolution: Fixed
Fixed in: http://svn.apache.org/viewvc?view=revision&revision=1654765
> Problematic directory entry check in ProviderBundleTrackerCustomizer
> --------------------------------------------------------------------
>
> Key: ARIES-1289
> URL: https://issues.apache.org/jira/browse/ARIES-1289
> Project: Aries
> Issue Type: Bug
> Components: SPI Fly
> Affects Versions: spifly-1.0.1
> Reporter: David Bosschaert
> Assignee: David Bosschaert
> Fix For: spifly-1.0.2
>
>
> See http://aries.15396.n3.nabble.com/Aries-spi-fly-Directory-entry-check-in-ProviderBundleTrackerCustomizer-td4030075.html
> In short: lines 109-111 of ProviderBundleTrackerCustomizer.java contain a check that is both problematic if the bundle does not contain directory entries and also unnecessary:
> {code}URL servicesDir = bundle.getResource("/" + METAINF_SERVICES);
> if (servicesDir == null)
> return null;{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)