[
https://issues.apache.org/jira/browse/CMIS-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067948#comment-16067948
]
Edward Wolthuis commented on CMIS-1036:
---------------------------------------
Furthermore, in my use cases, the client code is unaware of the ID of the
latest version of a resource, which is why I'm using the findByPath version.
But that's not really relevant for my problem, which occurs in both the
findByPath and findById versions.
> As a Developer I want to be able to use a CMIS selector (or not) when
> retrieving Objects
> ----------------------------------------------------------------------------------------
>
> Key: CMIS-1036
> URL: https://issues.apache.org/jira/browse/CMIS-1036
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-client-bindings
> Affects Versions: OpenCMIS 1.1.0
> Reporter: Edward Wolthuis
>
> When retrieving a Folder via plain HTTP, without using a cmisselector
> parameter (i.e. GET http://example.com/cmis/repository/123/myFolder), the
> Specs define that a value of 'children' will be used to return the result.
> (see section 5.4 at
> http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1-errata01-os-complete.html#x1-5580004)
> When using the browser bindings, object retrieval by using the path (i.e.
> /123/MyFolder) always seems to use a cmisselector parameter with the value of
> 'object', making it impossible to reproduce the result above. (actually, all
> Object finders)
> (see
> org.apache.chemistry.opencmis.client.bindings.spi.browser.ObjectServiceImpl)
> Why not let the user decide to use a cmisselector (for example in the
> Operation Context), or not?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
