Affects Version/s: None
Fix Version/s: 2.0
Currently, the method for locating resources (ie ConfigurationUtils.locate )
uses a few means of finding the resource. However, the ways of finding resources
are set in stone.
At times, it would be useful to be able to pick and choose how resources are
located. Here's an example:
I have a webapp that builds a CompositeConfiguration composed of several
PropertiesConfigurations (we'll say my.properties and default.properties) via
spring. So, I go to kick off tomcat. If the current directory I'm in has a
my.properties or default.properties.... those files get used instead of the ones
on the classpath that I intended to be used. As a result, unexpected behavior of
the webapp ensues.
The solution to this is to encapsulate each algorithm for locating resoucess,
and be able to pick and choose. To me, this screamed of the strategy pattern.
A patch is forthcoming...