You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/15 22:33:40 UTC
[jira] [Resolved] (CONFIGURATION-476) Possible ClassCastException
in CompositeConfiguration if a special in-memory configuration is used
[ https://issues.apache.org/jira/browse/CONFIGURATION-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger resolved CONFIGURATION-476.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.8
Fixed in revision 1231760.
> Possible ClassCastException in CompositeConfiguration if a special in-memory configuration is used
> --------------------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-476
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-476
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.7
> Reporter: Oliver Heger
> Assignee: Oliver Heger
> Fix For: 1.8
>
>
> Some methods of {{CompositeConfiguration}} expect that the in-memory configuration is of type {{BaseConfiguration}} (a configuration of this type is created if no specific in-memory configuration was provided).
> However, there are constructors accepting an arbitrary {{Configuration}} object as in-memory configuration. If here a configuration is specified which does not extend {{BaseConfiguration}}, the casts performed by these methods will fail. The casts should only be performed if possible.
> The following methods are affected:
> * _setListDelimiter()_
> * _setDelimiterParsingDisabled()_
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira