You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Mike Noordermeer (JIRA)" <ji...@apache.org> on 2011/03/01 17:35:36 UTC

[jira] Updated: (CONFIGURATION-438) JNDIConfiguration logs Exception when prefix does not exist

     [ https://issues.apache.org/jira/browse/CONFIGURATION-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Noordermeer updated CONFIGURATION-438:
-------------------------------------------

    Attachment: namenotfoundexception.patch

> JNDIConfiguration logs Exception when prefix does not exist
> -----------------------------------------------------------
>
>                 Key: CONFIGURATION-438
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-438
>             Project: Commons Configuration
>          Issue Type: Bug
>          Components: Events & Notifications
>    Affects Versions: 1.6, Nightly Builds
>            Reporter: Mike Noordermeer
>            Priority: Trivial
>         Attachments: 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: http://www.atlassian.com/software/jira