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=31111>. 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=31111 [configuration] Composite Configuration does not catch error on a Configuration entry [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2004-09-10 13:45 ------- Actually, I think that if there is an error, then CompositeConfiguration should propagate that error.. C-C assumes that the underlying configurations setup works.. That's why there isn't any "startup" phase where we validate a list of configurations and see if they are working or not. At a minimum, we could change it to throw a nice exception.. Just logging it means though that someone might not discover until later that their confiugraiton setup was wrong.. round about when they are wondering why things don't work properly.. I can see the people saying "I put debug.on in jndi, why won't it work" and later discover that they misconfigured, but C-C hid it. I would recommend that you attach a unit test to TestCompositeConfiguration showing the error and then reopen this issue. maybe we add a swtich to CompositeConfiguration like ignoreBadConfigurations() or somethign... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
