[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-369) ACLs:
[ http://tools.oasis-open.org/issues/browse/CMIS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605#action_13605 ] Al Brown commented on CMIS-369: ------------------------------- applyACL in the wsdl is: <xs:element name="applyACL"> <xs:complexType> <xs:sequence> <xs:element name="repositoryId" type="xs:string" minOccurs="1" maxOccurs="1" /> <xs:element name="objectId" type="xs:string" minOccurs="1" maxOccurs="1" /> <xs:element name="addACEs" type="cmis:cmisAccessControlEntryType" minOccurs="1" maxOccurs="unbounded" /> <xs:element name="removeACEs" type="cmis:cmisAccessControlEntryType" minOccurs="1" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="applyACLResponse"> <xs:complexType> <xs:sequence> <xs:element name="ACEs" type="cmis:cmisAccessControlEntryType" minOccurs="1" maxOccurs="unbounded" /> <xs:element name="exact" type="xs:boolean" /> </xs:sequence> </xs:complexType> </xs:element> Both are ACE's. I would prefer ACL since it allows xs:any and the client and server can extend with info on the list rather than just per each ace. That's a nit though. Will fix lowercasing cmis perms in 62f. > ACLs: > ------ > > Key: CMIS-369 > URL: http://tools.oasis-open.org/issues/browse/CMIS-369 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Bug > Reporter: Paul Goetz > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]