[
https://issues.apache.org/jira/browse/OAK-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290263#comment-13290263
]
Julian Reschke commented on OAK-131:
------------------------------------
Jukka's proposal (see
http://mail-archives.apache.org/mod_mbox/jackrabbit-oak-dev/201206.mbox/%3CCAOFYJNY4DgwpBPrxDp71t2vsMyOt3+jwmeq2=qwfpay+fre...@mail.gmail.com%3E):
"Perhaps we should replace such cases with conflict markers that
prevent the transient space from being resolved (for example with a
commit hook that prevents such markers from being present in commit).
Only if the session then explicitly removes or re-adds the modified
subtree, thus clearing the conflict marker, can the save succeed."
> Session.save() silently discards pending changes
> ------------------------------------------------
>
> Key: OAK-131
> URL: https://issues.apache.org/jira/browse/OAK-131
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Julian Reschke
>
> SessionTest.testSaveInvalidStateException fails in OAK because save()
> implicitly calls refresh(true) (which is good), but refresh(true) discards
> pending changes (because the node being modified is gone in persistent
> storage).
> See also mail thread starting here:
> http://mail-archives.apache.org/mod_mbox/jackrabbit-oak-dev/201206.mbox/browser
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
