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

Alan Gairey commented on CMIS-876:
----------------------------------

I see your point that a query hit could be a combination of a number of objects.

In our particular case (where a query hit does correspond to a single object), 
after a query we then have to request the full object data for each hit in a 
separate request in order to get each object's links. This causes a significant 
performance slowdown. Are there any recommendations for how we could get this 
data in a single request?

Thanks.

> In AtomPub bindings, output full Atom entries in response to CMIS query 
> command
> -------------------------------------------------------------------------------
>
>                 Key: CMIS-876
>                 URL: https://issues.apache.org/jira/browse/CMIS-876
>             Project: Chemistry
>          Issue Type: Improvement
>          Components: opencmis-server
>    Affects Versions: OpenCMIS 0.12.0
>            Reporter: Alan Gairey
>         Attachments: full-atom-entries-in-query-response.diff
>
>
> Currently, in the AtomPub feed returned in response to a CMIS query command, 
> the Atom entry included for each hit does _not_ include the Atom links for 
> that entry.
> It would be useful if the Atom entries in the response also included their 
> links (self link, edit link, etc.).
> I believe this can be done by replacing the call to writeQueryResultEntry at 
> line 187 in DiscoveryService.java:
> {code}
> writeQueryResultEntry(entry, result, "id-" + idCounter, now, cmisVersion);
> {code}
> with a call to the writeObjectEntry method instead:
> {code}
> writeObjectEntry(service, entry, result, null, repositoryId, null, null, 
> baseUrl, false, cmisVersion);
> {code}
> I have attached an svn diff file with the changes.
> With this change, each Atom entry in the response also includes all its 
> defined Atom links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to