[jira] Assigned: (RIVER-9) PreferredClassLoader should try to avoid making a direct check against the first URL

["Mark Brouwer (JIRA)" <ji...@apache.org>]

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

Mark Brouwer reassigned RIVER-9:
--------------------------------

    Assignee: Mark Brouwer

> PreferredClassLoader should try to avoid making a direct check against the first URL
> ------------------------------------------------------------------------------------
>
>                 Key: RIVER-9
>                 URL: https://issues.apache.org/jira/browse/RIVER-9
>             Project: River
>          Issue Type: Improvement
>            Reporter: Mark Brouwer
>         Assigned To: Mark Brouwer
>            Priority: Minor
>
> {{net.jini.loader.pref.PreferredClassLoader}} currently performs a direct check against the first URL to see whether the there is a {{PREFERRED.LIST}}. The reasons for this direct request instead of attempting to access through a "jar:" URL is because the "jar:" protocol handler can mask between definite lack of existence and less definitive errors.
> The side effect of the current approach is explained in this [posting|http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200701.mbox/%3c45A3F189.8040809@cheiron.org%3e]. An improvement that would not result in bypassing a JAR file cache in case the first JAR file is locally available is given in this [posting|http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200701.mbox/%3c45ADE8D2.5030904@cheiron.org%3e].

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