You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@chemistry.apache.org by "Florian Müller (JIRA)" <ji...@apache.org> on 2013/01/03 17:34:13 UTC

[jira] [Resolved] (CMIS-605) non-optional getTypeDescendants and getAllowableActions in AbstractCmisService

     [ https://issues.apache.org/jira/browse/CMIS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Müller resolved CMIS-605.
---------------------------------

       Resolution: Fixed
    Fix Version/s: OpenCMIS 0.9.0
         Assignee: Florian Müller

"Optional" means that many clients can live without them. It doesn't mean the repository would be spec compliant.
Nevertheless, both methods now have a convenience implementation.
                
> non-optional getTypeDescendants and getAllowableActions in AbstractCmisService
> ------------------------------------------------------------------------------
>
>                 Key: CMIS-605
>                 URL: https://issues.apache.org/jira/browse/CMIS-605
>             Project: Chemistry
>          Issue Type: Improvement
>    Affects Versions: OpenCMIS 0.8.0
>            Reporter: Michael Brackx
>            Assignee: Florian Müller
>            Priority: Minor
>             Fix For: OpenCMIS 0.9.0
>
>
> getTypeDescendants and getAllowableActions are marked optional and implemented in AbstractCmisService, however they are required to pass the tck BasicsTestGroup

--
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