[CMIS-461] AtomPub: cannot get folder rendition by stream id

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: OpenCMIS 0.5.0
• Fix Version/s: OpenCMIS 0.6.0
• Component/s: opencmis-client-bindings
• Assignee: Florent Guillaume
• Reporter: Florent Guillaume
• Created: 27/Oct/11 18:21
• Updated: 02/May/13 02:29
• Resolved: 27/Oct/11 18:25

Description

Using AtomPub, the spec says that the URL for a rendition stream is in the <link rel="alternate" href="...">, however these alternate link definitions don't contain the stream id. So if all you have is a stream id (as returned in the <cmis:rendition> elements for instance), it's not enough.

So using AtomPub it's impossible to implement properly a getContentStream with a streamId parameter. That's a spec deficiency, as already pointed out in http://lists.oasis-open.org/archives/cmis/201002/msg00021.html

In the current implementation, an attempt is made to add ?streamId=... to the content stream URL, and apparently most servers accept that, even though this is not per spec. But a folder (which may have a rendition) does not have a content stream so this cannot work at all in the folder case.

One possibility to fix this is to try to extract a meaningful stream id from the alternate links by parsing the link URL and extracting any streamId=... parameter found. Note that this is only a workaround, as nothing in the spec mandates that the URL be of this form.

Issue Links

• is depended upon by: CMIS-454 Can't get folder's rendition when using Nuxeo (length != -1, contentStream = null)