commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CONFIGURATION-438) JNDIConfiguration logs Exception when prefix does not exist
Date Tue, 15 Mar 2011 21:20:29 GMT

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

Oliver Heger resolved CONFIGURATION-438.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.7

Patch applied in revision 1081926. A unit test was added, too.

Many thanks!

> 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
>            Assignee: Oliver Heger
>            Priority: Trivial
>             Fix For: 1.7
>
>         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: http://www.atlassian.com/software/jira

Mime
View raw message