[RIVER-191] ConfigurationFile spec should state which classloader is used to search for prohibited methods

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: net_jini_config
• Bugtraq ID: 6315269
• Assignee: Unassigned
• Reporter: Brian Murphy
• Created: 04/Aug/07 17:18
• Updated: 04/Aug/07 17:18

Description

Bugtraq ID 6315269

Related Bugs 6316685 , 6316686 , 6316689
Submit Date 24-AUG-2005

Description
ConfigurationFile provides a mechanism for extending the set of methods which
should not be used in a configuration source. This mechanism consists of adding
a resource, net/jini/config/resources/ConfigurationFile.moreProhibitedMethods,
containing additional methods to add to the prohibited set. The, spec, however
does not state that ConfigurationFile uses its classloader, not the context classloader
or the classloader passed in to its constructor, to search for this resource.

Posted Date : 2005-08-24 14:55:50.0

It may also be useful to extend the prohibited methods mechanism to allow
applications using ConfigurationFile to define their own set of prohibited methods;
this would entail changing ConfigurationFile so that it searches for the net/jini/config/resources/ConfigurationFile.moreProhibitedMethods resource in the context
classloader/classloader-passed-in-to-its-constructor as well as in its own classloader.
The set of prohibited methods would be the union of the methods statically defined,
the methods listed in the resource in ConfigurationFile's class loader, and the methods
listed in the resource in the context classloader/passed-in classloader.

Posted Date : 2005-08-24 17:19:57.0

Work Around
N/A