[
https://issues.apache.org/jira/browse/SLING-12264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825158#comment-17825158
]
Carsten Ziegeler commented on SLING-12264:
------------------------------------------
This sounds like a fix at the wrong place; I would expect that session.save()
is actually doing exactly the same internally - in which case this extra check
introduces a penality as it is then called twice.
> check save() operations
> -----------------------
>
> Key: SLING-12264
> URL: https://issues.apache.org/jira/browse/SLING-12264
> Project: Sling
> Issue Type: Task
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.46
> Reporter: Joerg Hoh
> Priority: Major
>
> Before doing a session.save() operation, it should always be checked if there
> is something to save at all.
> This can speed up the execution of individual repoinit statements if the
> repoinit statement does not need to be applied.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
