linzhixing created CMIS-678:
-------------------------------
Summary: orderBy parameter is not required by CMIS spec for
getCheckedOutDocs / getChildren, but TCK requires it
Key: CMIS-678
URL: https://issues.apache.org/jira/browse/CMIS-678
Project: Chemistry
Issue Type: Bug
Affects Versions: OpenCMIS 0.9.0 beta 1
Reporter: linzhixing
Priority: Minor
TCK says to me
"Checked-out documents should be ordered by cmis:name, but they are not! (It
might be a collation mismatch.)", from CheckedOutTest.java LINE:133.
This is also the case with the test of getChildren.
In CMIS1.1 spec 2.2.3.6, there is nothing to demand the outputs are ordered by
cmis:name.
What is worse, when CapabilityOrderBy is set to NONE, TCK CheckedOutTest
doesn't take it into consideration.
Basically, if a repository sets capabilityOrderBy to NONE and a client sends
orderBy parameter, what should the repository do? To neglect the parameter
silently or to throw a CmisInvalidArgument error? If the former, I expect TCK
skip the order-compiant test and if the latter, I expect TCK avoid sending
orderBy parameter in advance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
