You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2007/01/20 20:00:29 UTC
[jira] Resolved: (CONFIGURATION-245) DatabaseConfiguration and
JNDIConfiguration are eating exceptions
[ https://issues.apache.org/jira/browse/CONFIGURATION-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger resolved CONFIGURATION-245.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.4
The concept of error listeners was implemented. It is now possible for an interested client to register itself as an error listener at a configuration. It is then notified about internal errors. DatabaseConfiguration, JNDIConfiguration, and AbstractFileConfiguration use this new concept for reporting internal errors.
> DatabaseConfiguration and JNDIConfiguration are eating exceptions
> -----------------------------------------------------------------
>
> Key: CONFIGURATION-245
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-245
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: Nightly Builds, 1.3 Final
> Reporter: Hal Deadman
> Assigned To: Oliver Heger
> Fix For: 1.4
>
>
> 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: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org