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 2015/04/07 15:20:13 UTC

[jira] [Commented] (SLING-4585) Performance: Use JackrabbitSession#getItemOrNull to speed up JcrResourceProvider#createResource

    [ https://issues.apache.org/jira/browse/SLING-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483136#comment-14483136 ] 

Carsten Ziegeler commented on SLING-4585:
-----------------------------------------

We should make sure that the implementation still runs on older jackrabbit api versions and simply reverts to the old behaviour. Otherwise updating the jcr resource bundle requires updating the jcr implementation; we should avoid this

> Performance: Use JackrabbitSession#getItemOrNull to speed up JcrResourceProvider#createResource
> -----------------------------------------------------------------------------------------------
>
>                 Key: SLING-4585
>                 URL: https://issues.apache.org/jira/browse/SLING-4585
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR, ResourceResolver
>    Affects Versions: JCR Resource 2.5.0
>            Reporter: Joel Richard
>            Priority: Critical
>              Labels: performance
>
> If the current session is a JackrabbitSession, JcrResourceProvider should use getItemOrNull (as soon as exported) to save rendering time.
> See referenced issue and the following mail thread for more information: http://mail-archives.apache.org/mod_mbox/jackrabbit-oak-dev/201504.mbox/browser



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)