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 2013/12/10 00:36:07 UTC
[jira] [Updated] (SLING-3249) Cache not properly used in
JcrPropertyMap
[ https://issues.apache.org/jira/browse/SLING-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-3249:
------------------------------------
Fix Version/s: JCR Resource 2.3.0
> Cache not properly used in JcrPropertyMap
> -----------------------------------------
>
> Key: SLING-3249
> URL: https://issues.apache.org/jira/browse/SLING-3249
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.2.8
> Reporter: Przemo Pakulski
> Labels: perfomance
> Fix For: JCR Resource 2.3.0
>
>
> JcrPropertyMap class has internal cache for properties an values.
> The cache is not used correctly, e.g. reading the same property twice still results in access to underlying node.
> The problem is with get() methods, when property is red it is put into the cache, but the cache is never checked if it already contains the property.
> The only way to force the caching is to use readFully() method indirectly, in this case read method is examining the cache.
> It looks this has been introduced by fixing SLING-2425.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)