[jira] Updated: (CONFIGURATION-61) [configuration] JNDIConfiguration and union configuration

["Emmanuel Bourg (JIRA)" <ji...@apache.org>]

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

Emmanuel Bourg updated CONFIGURATION-61:
----------------------------------------

    Fix Version/s: 1.0

> [configuration] JNDIConfiguration and union configuration
> ---------------------------------------------------------
>
>                 Key: CONFIGURATION-61
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-61
>             Project: Commons Configuration
>          Issue Type: Bug
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Oliver Heger
>             Fix For: 1.0
>
>         Attachments: testconfigurationfactory.txt, testDigesterConfiguration3.xml
>
>
> JNDIConfiguration seems not to work with ConfigurationFactory when used in the
> <additional> section. The union configuration feature of ConfigurationFactory is
> implemented by calling getKeys() on a Configuration object, iterating through
> the keys, and calling getProperty() for each.
> JNDIConfiguration.getKeys() obviously always returns an empty iterator in my
> tests though the Configuration object is not empty (getString() returns values
> for some keys). I am not sure whether this is a bug in JNDIConfiguration or a
> shortcomming of the JNDI implementation used for testing.
> Another point is that JNDIConfiguration.getProperty() always throws a not
> supported error. This would also blow ConfigurationFactory if getKeys() returned
> a valid iterator. I don't understand why this error is thrown. In my opinion
> this is a violation of the contract defined by the Configuration interface (the
> same is true for some other methods).
> Attached is an extension to the unit test of ConfigurationFactory that
> demonstrates the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org