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=29611>. 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=29611 [configuration] MapConfiguration [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2004-08-12 16:05 ------- I am going with the name ConfigurationMap.. The reason is to follw HashMap, TreeMap, etc.. this somewhat implies that is is a Map backed by a Configuration. If it was MapConfiguration then following XmlConfiguration or JNDIConfiguration then it is a Configuration backed by a Map! It was a very nice clean patch. Just fixed up a couple @author tags. Would you mind however adding a more explicit testcase for ConfigurationSet? (Which I renamed from EntrySetConfiguration for similar reasons).. the code coverage previously was 88% percent and with EntrySetConfiguration being only at 68% it drops the average down to 87% percent. I know.. nitpicky, but I love the high unit test coverage configuration enjoys! Eric Pugh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
