commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Noordermeer (JIRA)" <>
Subject [jira] Updated: (CONFIGURATION-438) JNDIConfiguration logs Exception when prefix does not exist
Date Tue, 01 Mar 2011 16:36:42 GMT


Mike Noordermeer updated CONFIGURATION-438:

    Attachment: namenotfoundexception-correct.patch

The correct version of the patch, previous one included other, not relevant changes.

> JNDIConfiguration logs Exception when prefix does not exist
> -----------------------------------------------------------
>                 Key: CONFIGURATION-438
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Bug
>          Components: Events & Notifications
>    Affects Versions: 1.6, Nightly Builds
>            Reporter: Mike Noordermeer
>            Priority: Trivial
>         Attachments: namenotfoundexception-correct.patch, namenotfoundexception.patch
> A JNDIConfiguration logs an exception when it's prefix does not exist and getKeys() is
called. This is for instance the case when a JNDIConfiguration is used in a DefaultConfigurationBuilder.
It does not log an exception when a key does not exist when using getProperty() (that was
fixed in issue #44). This seems like an inconsistency to me. Attached patch fixes the problem
by ignoring the NameNotFoundException.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message