: Thursday, October 21, 2004 2:11 PM
To: Jakarta Commons Developers List
Subject: Re: [configuration] Concerns with ConfigurationRuntimeException
Emmanuel Bourg wrote:
Let me know if I missed an exception.
AFAIK, all actions throw the runtime exception ConversionException.
I'm not fond
Hi Ricardo,
Ricardo Gladwell wrote:
Hi All,
I recently noticed the addition of the ConfigurationException
ConfigurationRuntimeException exception classes. The API now throws a
mixture of both of these. As I mentioned earlier, I'm still concerned
with throwing a RuntimeException in the API.
Emmanuel Bourg wrote:
Let me know if I missed an exception.
AFAIK, all actions throw the runtime exception ConversionException.
I'm not fond of this. It only affects the configurations using an
unreliable communication channel to access the properties, that's
JNDIConfiguration and
Ricardo Gladwell wrote:
Emmanuel Bourg wrote:
Let me know if I missed an exception.
AFAIK, all actions throw the runtime exception ConversionException.
The typed getters only. getProperty, getKeys, isEmpty, addProperty,
setProperty, clear, clearProperty, subset, containsKey do not throw
Gladwell [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 21, 2004 2:11 PM
To: Jakarta Commons Developers List
Subject: Re: [configuration] Concerns with ConfigurationRuntimeException
Emmanuel Bourg wrote:
Let me know if I missed an exception.
AFAIK, all actions throw the runtime exception
Hi fellows,
Eric Pugh wrote on Thursday, October 21, 2004 4:30 PM:
I think both arguments are valid. It depends on your use
case.
[snip]
Could we have two interfaces? Configuration and
StrictConfiguration? StrictConfiguration would declare
checked methods?
What about a monitor
