DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39548>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39548 Summary: [configuration] use a Strategy pattern for locating resources Product: Commons Version: unspecified Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: Configuration AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] 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... -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
