[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-493) itemAlreadyExistsException missing
[ http://tools.oasis-open.org/issues/browse/CMIS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565#action_15565 ] Al Brown commented on CMIS-493: ------------------------------- I think the bar is pretty high. Exceptions are signaling mechanisms. Repositories might not be able to return a very granular exception but can a more general one. Also, with itemAlreadyExists, how can a client resolve it? What propertie(s) or fields must be changed so that the client can resubmit the failed request? Since we don't have a mechanism that allows a client to set the name, I am not sure if it is worth it on the client compared to a runtime exception or constraint exception (constraint is the same except more general). > itemAlreadyExists Exception missing > ----------------------------------- > > Key: CMIS-493 > URL: http://tools.oasis-open.org/issues/browse/CMIS-493 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Improvement > Components: Domain Model > Affects Versions: Draft 0.62 > Reporter: Martin Hermes > Assignee: Ethan Gur-esh > Priority: Minor > > A repository which does not support same name siblings should throw an itemAlreadyExists exception if a file or folder is created using a name which already exists as sibling. -- 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]