[OASIS Issue Tracker] Commented: (CMIS-260) Query XML Document isconfusing.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290#action_17290 ] 

Al Brown commented on CMIS-260:
-------------------------------

JIRA Cleanup

> Query XML Document is confusing.
> --------------------------------
>
>                 Key: CMIS-260
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-260
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>    Affects Versions: Draft 0.62
>            Reporter: Ryan McVeigh
>            Assignee: Al Brown
>             Fix For: Draft 0.62
>
>
> The query xml document has an element for repositoryId. However, the way the service document is set up and the fact that some repositories don't support query (or support it differently) makes me assume that the Query collection is expected to be per-repository. So what happens if you post a query document to one repository's query collection, and the document contains a repositoryId for a different repository?
> Proposal: Quit using this WS document for ReST. Query should be a GET, which takes a statement as a query param (with a reasonable default, like "SELECT * FROM Document").
> I realize the query GET issue has come up more than once, but it keeps coming up internally for a reason, and this is another example.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira