[
https://issues.apache.org/jira/browse/CMIS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731898#action_12731898
]
Florent Guillaume commented on CMIS-40:
---------------------------------------
As a client implementor you may very well want to deal with the SPI, if you
want performance. The Connection is for convenience, the SPI for performance
and actual implementation. If you know you want the titles of docs 102800 to
102810 of a query, then the SPI is the way to go.
You haven't told us really *why* you need to pass the additional arguments to
the query. Do you want batching? If so, then that's legitimate but the way I'd
like to have this is through the returned collection-like object, not using
explicit arguments.
Currently Collection isn't intelligent enough, we should probably return an
Iterator, or a skippable iterator à la
http://www.day.com/maven/jsr170/javadocs/jcr-1.0/javax/jcr/RangeIterator.html
Would that work for you?
> query method with full parameters should be exposed as part of the Connection
> interface
> ---------------------------------------------------------------------------------------
>
> Key: CMIS-40
> URL: https://issues.apache.org/jira/browse/CMIS-40
> Project: Chemistry
> Issue Type: Improvement
> Components: atompub, client
> Reporter: Ugo Cei
>
> The following method of APPConnection:
> {code}
> public Collection<ObjectEntry> query(String statement,
> boolean searchAllVersions,
> boolean includeAllowableActions,
> boolean includeRelationships,
> int maxItems, int skipCount,
> boolean[] hasMoreItems)
> {code}
> is not declared for the Collection interface, therefore it's not possible to
> specify parameters for a query without downcasting to APPCollection.
> Also, the method should return a Collection<CMISObject> for conformance with
> the existing query method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
