You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/01/14 16:00:53 UTC
[jira] [Issue Comment Deleted] (SLING-4307) Avoid caching JCR
property values
[ https://issues.apache.org/jira/browse/SLING-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig updated SLING-4307:
---------------------------------
Comment: was deleted
(was: Yes it mostly does. Best thing is to acquire from the parent property when needed.)
> Avoid caching JCR property values
> ---------------------------------
>
> Key: SLING-4307
> URL: https://issues.apache.org/jira/browse/SLING-4307
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.4.0
>
>
> The support for ValueMap is currently caching the JCR Value objects and also the JCR Property object.
> If the value map object is held, this might prevent garbage collection within Oak as the value object holds a reference to the revision.
> We should check whether caching is needed at all or if for example we could just cache the value itself but not the JCR Value object
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)