[
https://issues.apache.org/jira/browse/CMIS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florent Guillaume resolved CMIS-461.
------------------------------------
Resolution: Fixed
r1189924
> AtomPub: cannot get folder rendition by stream id
> -------------------------------------------------
>
> Key: CMIS-461
> URL: https://issues.apache.org/jira/browse/CMIS-461
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-client-bindings
> Affects Versions: OpenCMIS 0.5.0
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
> Priority: Minor
> Fix For: OpenCMIS 0.6.0
>
>
> 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.
--
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
