Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <31779212.1193342630587.JavaMail.jira@brutus>
Date: Thu, 25 Oct 2007 13:03:50 -0700 (PDT)
From: "Oliver Heger (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Resolved: (CONFIGURATION-299) Interpolation of ${const:xxx}
 variables can cause a ClassCastException
In-Reply-To: <5609686.1193341791926.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Oliver Heger resolved CONFIGURATION-299.
----------------------------------------

    Resolution: Fixed

A fix was applied for this issue.

> Interpolation of ${const:xxx} variables can cause a ClassCastException
> ----------------------------------------------------------------------
>
>                 Key: CONFIGURATION-299
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-299
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.4
>            Reporter: Oliver Heger
>            Assignee: Oliver Heger
>             Fix For: 1.5
>
>
> If ConstantLookup is used for resolving a variable that is of a different type than String, a ClassCastException can be thrown:
> The first access to this variable obtains the value and stores it in an internal cache. If this variable is requested again, the value is fetched from the cache and a type cast to String is performed. This will fail with a ClassCastException.

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