[RIVER-19] PreferredClassLoader doesn't implement preferred semantics for getResources(String)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: jtsk_2.1
• Fix Version/s: River_3.0.0
• Component/s: net_jini_loader
• Assignee: Unassigned
• Reporter: Mark Brouwer
• Created: 30/Mar/07 06:00
• Updated: 05/Dec/15 09:07
• Resolved: 05/Dec/15 09:07

Description

While PreferredClassLoader.getResource(String) obeys preferred classes semantics, there is no overridden getResources(String) method that does the same. This can lead to nasty consequences with the service provider mechanism as is used throughout the JDK and JTSK code, namely definitions for service providers are made visible through getResources(String) while the implementing classes might have been shielded due to the PREFERRED.LIST effective.

Up to J2SE 1.4.2 it was not possible to implement preferred classes semantics as ClassLoader.getResources(String) was declared final, but as soon as the Jini specs require J2SE 5.0 as minimum we are safe to implement the correct behavior for PreferredClassLoader.getResources(String), see also JDC bug 4432218.