DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26694>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26694 BaseConfiguration: containsKey ignores default properties ------- Additional Comments From [EMAIL PROTECTED] 2004-02-16 13:47 ------- I'm answering here because I'm not subscribed to the list. I actually switched from PropertiesConfiguration with default values to CompositeConfiguration after discovering this bug. My initial reason for not using CompositeConfiguration was a documentation bug: CompositeConfiguration.addProperty says "CompositeConfigurations can not be added to". Luckily, this isn't true (would have been a blocker for me if it were), but I had to check the source code to find out. Otherwise I'm quite happy with using CompositeConfiguration instead of chained defaults, but there is still one problem: CompositeConfiguration live in memory only, I cannot store them. Currently I could convert a CompositeConfiguration to a PropertiesConfiguration via the PropertiesConfiguration(Configuration defaults) constructor for storing it, but if you remove the defaults that would no longer be possible. Is there another way for converting a CompositeConfiguration to a serializable format, or could you add one? If yes, I think it a good idea to replace chained defaults by CompositeConfiguration. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
