aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARIES-1289) Problematic directory entry check in ProviderBundleTrackerCustomizer
Date Mon, 26 Jan 2015 11:27:34 GMT

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

David Bosschaert updated ARIES-1289:
------------------------------------
          Component/s: SPI Fly
    Affects Version/s: spifly-1.0.1
        Fix Version/s: spifly-1.0.2
              Summary: Problematic directory entry check in ProviderBundleTrackerCustomizer
 (was: [Spi-fly] Problematic directory entry check in ProviderBundleTrackerCustomizer)

> 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)

Mime
View raw message