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

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

A CMIS spec compliant AtomPub response MUST contain links to ALL relationships 
(= BOTH relationship directions). The links in the response MUST NOT depend on 
the input or any configuration. The generic implementation is correct. The 
hardcoded BOTH value is only way to produce a spec compliant response. There is 
no bug or potential for optimization here.

A repository specific {{getObjectInfo()}} implementation might use a better way 
to retrieve these relationship IDs. It might also choose to return a spec 
in-compliant response, but that’s not something we should encourage in OpenCMIS.

> AbstractCmisService class is not taking inputs as passed in the ObjectService
> -----------------------------------------------------------------------------
>
>                 Key: CMIS-1107
>                 URL: https://issues.apache.org/jira/browse/CMIS-1107
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-commons
>            Reporter: Manisha Sapiah
>            Assignee: Florian Müller
>            Priority: Blocker
>         Attachments: image-2020-09-21-19-10-45-895.png
>
>
> Whenever we are trying to getObject for atompub binding, we see the parameter 
> includeRelationships is set to BOTH in the AbstractCmisService 
> (*getObjectInfo:1059, AbstractCmisService 
> (org.apache.chemistry.opencmis.commons.impl.server)* due to method 
> getObjectInfo.
> While the value passed in the ObjectService is NONE *(class serve:470, 
> ObjectService$GetObject (org.apache.chemistry.opencmis.server.impl.atompub)* 
> which can be seen in the attachment:
> !image-2020-09-21-19-10-45-895.png!
> This is causing a behavior change and a performance issue.
> We are using chemistry-opencmis-0.13.0 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to