[
https://issues.apache.org/jira/browse/CMIS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Potts resolved CMIS-170.
-----------------------------
Resolution: Fixed
I think this is a lame piece of the spec. A filter should filter or it should
have a capability set to "None", but I suppose that is an issue to take up with
OASIS.
In the meantime, I've updated the test to not look for properties that would be
filtered out. It does look for properties it asks for in the filter, which
should be returned whether or not the server actually filters the list.
> cmislib testPropertyFilter is wrong
> -----------------------------------
>
> Key: CMIS-170
> URL: https://issues.apache.org/jira/browse/CMIS-170
> Project: Chemistry
> Issue Type: Bug
> Components: cmislib
> Reporter: Florent Guillaume
> Assignee: Jeff Potts
>
> testPropertyFilter assumes that when getting an object (by path) with a
> properties filter, it will not received any additional properties, for
> instance cmis:name in the test.
> But this is wrong, the spec doesn't disallow more properties, it just says ยง
> 2.2.1.2.1 "Properties": Repositories SHOULD return only the properties
> specified in the property filter if they exist on the object's type
> definition.
> It's a SHOULD, not a MUST.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
