Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <373074789.1249973174801.JavaMail.jira@brutus>
Date: Mon, 10 Aug 2009 23:46:14 -0700 (PDT)
From: "Henri Yandell (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (LANG-494) CharSet sub-classes cannot be made
 thread-safe
In-Reply-To: <1110150131.1237130810436.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LANG-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741723#action_12741723 ] 

Henri Yandell commented on LANG-494:
------------------------------------

So, do we wrap it in a synchronized call?

> CharSet sub-classes cannot be made thread-safe
> ----------------------------------------------
>
>                 Key: LANG-494
>                 URL: https://issues.apache.org/jira/browse/LANG-494
>             Project: Commons Lang
>          Issue Type: Bug
>            Reporter: Sebb
>             Fix For: 3.0
>
>
> AFAICT, CharSet sub-classes cannot be made thread-safe.
> This is because the HashMap and HashSet collections are not thread-safe.
> If a sub-class updates COMMON, there is no guarantee that getInstance() will see the update.
> In the case of the instance variable "set", the sub-class could override all the read/write methods to provide thread-safety.

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