[
https://issues.apache.org/jira/browse/JCR-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-1209:
----------------------------------
Attachment: JCR-1209.patch
I suggest we implement a check for pending changes. For most cases this also
allows us to commit the changes to the two properties atomically. Currently
there are always two save calls and if the first one fails, the workspace is
inconsistent. The patch also adds a refresh in case the session save fails.
It's not the perfect solution, but IMO better than what we currently have.
> NodeImpl.checkout() calls save() two times
> ------------------------------------------
>
> Key: JCR-1209
> URL: https://issues.apache.org/jira/browse/JCR-1209
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core, versioning
> Reporter: Przemo Pakulski
> Priority: Minor
> Fix For: 1.4
>
> Attachments: JCR-1209.patch
>
>
> Similar to JCR-975, The version related properties on a versionable node that
> is checked out are saved individually. There is no need to save them
> individually because checkd in node must not have pending changes and save()
> can be called safely on the node itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
