[RIVER-9] PreferredClassLoader should try to avoid making a direct check against the first URL

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: jtsk_2.1
• Fix Version/s: River_2.1.2
• Component/s: net_jini_loader
• Assignee: Mark Brouwer
• Reporter: Mark Brouwer
• Created: 24/Jan/07 17:22
• Updated: 09/Mar/08 12:47
• Resolved: 10/Feb/08 12:21

Description

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