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

Florian Müller commented on CMIS-1036:
--------------------------------------

The OpenCMIS (high-level) API is binding agnostic. The cmiselector only exists 
for the Browser binding. The other two binding don't have such a concept. 
Therefore, such a feature would only makes sense in the low-level API (which 
nobody directly uses).

What is your use case for such an addition?

Accessing data by path instead of by ID (which is what you are asking for) is 
just a different way of composing the URL. The result should be the same. There 
is nothing that you cannot access by ID that you can access by path.

> 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)

Reply via email to