[ https://issues.apache.org/jira/browse/JCR-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1209: ------------------------------- Component/s: jackrabbit-core Affects Version/s: (was: 1.3.3) (was: 1.4) As far as performance is concerned, the save() call is by far the most expensive operation, so getting rid of the second call would definitely be nice. But I agree with Stefan that it might not be worth the extra complexity in code. Could (should?) we make the checkout operation work on a lower level, parallel to what save() does? That would nicely clean up the logic. > NodeImpl.checkot() 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 > > > 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.