[
https://issues.apache.org/jira/browse/RIVER-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Firmstone resolved RIVER-19.
----------------------------------
Resolution: Fixed
Fix Version/s: River_3.0.0
This method has been added in PreferredClassLoader and annotated with @since
3.0.0
> PreferredClassLoader doesn't implement preferred semantics for
> getResources(String)
> -----------------------------------------------------------------------------------
>
> Key: RIVER-19
> URL: https://issues.apache.org/jira/browse/RIVER-19
> Project: River
> Issue Type: Bug
> Components: net_jini_loader
> Affects Versions: jtsk_2.1
> Reporter: Mark Brouwer
> Fix For: River_3.0.0
>
>
> 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|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4432218].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
