commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-245) DatabaseConfiguration and JNDIConfiguration are eating exceptions
Date Sat, 30 Dec 2006 16:53:22 GMT
Oliver Heger commented on CONFIGURATION-245:

Simply swallowing exceptions is certainly no good design. I agree that this should be changed.

I wonder however if we should always throw runtime exceptions when such an internal error
occurs. Maybe it would be better to make this behavior configurable. If the default behavior
was to just log the exception, we would keep compatibility with earlier versions, but allow
our users to change this.

One way this could be achieved would be to enhance the existing event mechanism. In addition
to normal configuration update events special error events could be generated. Interested
parties could register themselves as error listeners at a configuration and would then be
notified whenever a problem occurs.

What do you think, would such an approach make sense?

> DatabaseConfiguration and JNDIConfiguration are eating exceptions
> -----------------------------------------------------------------
>                 Key: CONFIGURATION-245
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: Nightly Builds, 1.3 Final
>            Reporter: Hal Deadman
> DatabaseConfiguration and JNDIConfiguration and possibly others, really need to throw
some sort of runtime exception to let the caller know the properties couldn't be read. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message