Hi Michael,
There is a general rule in CMIS 1.0 and CMIS 1.1 that multi-value
properties are not orderable.
CMIS 1.0 spec, section 2.1.3.3.2 (Attributes common to ALL Object-Type
Property Definitions):
"
orderable Boolean
Indicates whether the property can appear in the ORDER BY clause of a
CMIS query statement or an ORDERBY parameter.
This property MUST be FALSE for any property whose cardinality is
"multi".
"
Florian
Hi,
On trunk the TCK was changed to enforce that
allowedChildObjectTypeIds
is not orderable.
As far as i can tell, this is not a requirement for cmis 1.0
repositories.
Should this not be conditional on the cmis version?
Or is there a general rule somewhere in 1.0 that multi valued
properties are not orderable?
Michael
