You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/12/20 15:55:06 UTC

[jira] Closed: (SLING-1871) JcrResourceBundle.loadFully not thread safe

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

Carsten Ziegeler closed SLING-1871.
-----------------------------------


> JcrResourceBundle.loadFully not thread safe
> -------------------------------------------
>
>                 Key: SLING-1871
>                 URL: https://issues.apache.org/jira/browse/SLING-1871
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: I18n 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: I18n 2.0.4
>
>
> The JcrResourceBundle.loadFully method is intended to ensure the resource bundle is fully loaded (used by the getKeys() method).
> This method is not currently thread safe in that it writes into the resources (cache) map unsynchronized which may cause map corruption and thus endless loops.
> While fixing this method, we should also overwrite the Java 1.6 ResourceBundle method handleKeySet() which is used by the new keySet() method. The default implementation creates its own cache of keys, which duplicates the resource properties map of the JcrResourceBundle class.

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