You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2010/02/25 14:43:27 UTC
[jira] Issue Comment Edited: (JCR-2104) JSR 283 Full Versioning
[ https://issues.apache.org/jira/browse/JCR-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838336#action_12838336 ]
angela edited comment on JCR-2104 at 2/25/10 1:42 PM:
------------------------------------------------------
Revision: 916278 [work in progress, tested using jcr2dav-ConformanceTest]
jcr2spi:
- simplify VersionManager.checkpoint if Node is already checkedin
spi2dav + server-side implementation in jcr-server
- implement checkpoint as separate checkin-checkout [tmp. solution]
- implement shallow merge using custom extension of the MERGE request body [DAV:depth element]
spi2dav : bug fixes
- merge (besteffort <-> DAV:no-auto-merge)
- restore (nodeId may point to non-existing node -> extract existing parent + relPath
server-side:
- fix bug in server-side merge. for 1:1 remoting the MERGE response body should list the failed ids instead of the affected
resource [DeltaV specified behaviour that doesn't make sense for remoting over SPI]
- fix bug in restore with relPath
was (Author: anchela):
Revision: 916278 [work in progress]
jcr2spi:
- simplify VersionManager.checkpoint if Node is already checkedin
spi2dav + server-side implementation in jcr-server
- implement checkpoint as separate checkin-checkout [tmp. solution]
- implement shallow merge using custom extension of the MERGE request body [DAV:depth element]
spi2dav : bug fixes
- merge (besteffort <-> DAV:no-auto-merge)
- restore (nodeId may point to non-existing node -> extract existing parent + relPath
server-side:
- fix bug in server-side merge. for 1:1 remoting the MERGE response body should list the failed ids instead of the affected
resource [DeltaV specified behaviour that doesn't make sense for remoting over SPI]
- fix bug in restore with relPath
> JSR 283 Full Versioning
> -----------------------
>
> Key: JCR-2104
> URL: https://issues.apache.org/jira/browse/JCR-2104
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-jcr-server, jackrabbit-jcr2spi, jackrabbit-spi, jackrabbit-spi2dav, jackrabbit-spi2jcr, JCR 2.0
> Reporter: angela
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.