[
https://issues.apache.org/jira/browse/SLING-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936629#comment-14936629
]
Carsten Ziegeler commented on SLING-4585:
-----------------------------------------
I think we don't need the test. This is not testing the Sling code, but it's
testing whether getItemOrNull is doing the right thing
If we have to do some testing here and need the new API, then we have to
hand-craft the package import for the packages. Otherwise we're bound to the
latest version anyway.
And we really should not have SNAPSHOT dependencies to other projects in Sling.
This makes building Sling way too hard
> 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
> Attachments:
> 0001-SLING-4585-Performance-Use-JackrabbitSession-getItem.patch
>
>
> 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/%3CD1495A09.3B670%25anchela%40adobe.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
