[jira] Issue Comment Edited: (CMIS-181) Correct version history link in Atom binding

["Joeri Samson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CMIS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849648#action_12849648 ] 

Joeri Samson edited comment on CMIS-181 at 3/25/10 10:14 AM:
-------------------------------------------------------------

In the spec it only says that the version-history link must point to a feed with all the versions of a document. It doesn't say that feeds must have only 1 URL (unless this is implied by the Atom spec?), it also does not mention the version series id in relation to the version-history link

      was (Author: joeri):
    In the spec it only says that the version-history link must point to a feed with all the versions of a document. It doesn't say that feeds must have only 1 URL (unless this is implied by the Atom spec?), it also does not mention the version series id in relation to the version-history link.

I also don't think that the atom link filler has enough information to fill in the version series id by itself, though I could be wrong about that.
  
> Correct version history link in Atom binding
> --------------------------------------------
>
>                 Key: CMIS-181
>                 URL: https://issues.apache.org/jira/browse/CMIS-181
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-provider, opencmis-server, opencmis-server-inmemory
>            Reporter: Jens Hübel
>            Assignee: Jens Hübel
>            Priority: Minor
>
> Reported by Joeri Samson:
> The version-history link also did not work because the ID expected by the InMemoryVersioningService was the ID of the version series, while the ID in the atom link was that of the document itself (I changed the server to accept such links instead of changing the generated Atom links, because it did not seem to be possible to do this in a backend agnostic way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.