Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Date: Fri, 31 May 2013 07:42:20 +0000 (UTC)
From: =?utf-8?Q?Jaime_Porras_L=C3=B3pez_=28JIRA=29?= <jira@apache.org>
To: dev@chemistry.apache.org
Message-ID: <JIRA.12649880.1369827193772.45935.1369986140360@arcas>
In-Reply-To: <JIRA.12649880.1369827193772@arcas>
References: <JIRA.12649880.1369827193772@arcas>
Subject: [jira] [Commented] (CMIS-662) Incorrect PermissionMapping value
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CMIS-662?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D136712=
27#comment-13671227 ]=20

Jaime Porras L=C3=B3pez commented on CMIS-662:
-----------------------------------------

Thanks for the clarification. I have reviewed the schema and it's true that=
 the definition is "canGetDescendents.Folder". May be you could consider to=
 unify the specification with the schema.

Anyway, about the allowable action "canCreatePolicy" and the permission map=
ping "canCreatePolicy.Folder" defined in the CMIS 1.1 specification, could =
both of them be included in the schema and in the constants and enums of th=
e version 0.9.0?


               =20
> Incorrect PermissionMapping value
> ---------------------------------
>
>                 Key: CMIS-662
>                 URL: https://issues.apache.org/jira/browse/CMIS-662
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-commons
>    Affects Versions: OpenCMIS 0.8.0, OpenCMIS 0.9.0 beta 1
>            Reporter: Jaime Porras L=C3=B3pez
>            Priority: Minor
>
> org.apache.chemistry.opencmis.commons.data.PermissionMapping.CAN_GET_DESC=
ENDENTS_FOLDER value is:
> "canGetDescendents.Folder".
> According to the specifications 1.0 and 1.1, it should be:
> "canGetDescendants.Folder".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira