chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Florian Müller (JIRA) <>
Subject [jira] [Issue Comment Deleted] (CMIS-915) Discrepancy between specification and TCK tests
Date Tue, 26 May 2015 13:56:18 GMT


Florian Müller updated CMIS-915:
    Comment: was deleted

(was: There is a bit of confusion because there are two exact flags. There is one returned
by getACL, which is optional as you pointed out, and it is treated as optional by the TCK.
There is another exact flag attached to CMIS objects. The TCK complains about this one here.
Unfortunately, the spec isn't clear whether this is optional or not. (Might be a candidate
for the CMIS 1.1 errata.)

Changing the failure to a warning works for me. To be on the safe side, a server should always
set this flag, though.)

> Discrepancy between specification and TCK tests
> -----------------------------------------------
>                 Key: CMIS-915
>                 URL:
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-tck
>    Affects Versions: OpenCMIS 0.13.0
>            Reporter: Gavin Cornwell
>            Assignee: Florian Müller
> In 0.13.0 TCK tests started failing around the isExact flag, for example:
> {noformat}
> FAILURE: ACL ( [stacktrace]
>     FAILURE: ACL is provided but the isExact flag is not set! (
>         INFO: Object is null!
> {noformat}
> The spec [implies|]
that the isExact parameter is optional but the TCK now declares it must be set.
> Reducing the failure to a warning was hinted at on the mailing list, can this be done?

This message was sent by Atlassian JIRA

View raw message