[OASIS Issue Tracker] (CMIS-795) Add key to CMIS exceptions

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Florian Mueller updated CMIS-795:
---------------------------------

    Description: 
CMIS extensions consist of a type and a message. The type is fairly coarse grained. For example, there can be many reasons for a constraint exception. 
CMIS exceptions should get a third detail; something like a key that identifies the problem more precisely. Some of the values can be defined in the spec, but implementation specific values should also be allowed.

  was:
CMIS extensions consist of a type and a message. The type is fairly course grained. For example, there can be many reasons for constraint exception. 
CMIS exceptions should get a third detail; something like a key that identifies the problem more precisely. Some of the values can be defined in the spec, but implementation specific values should also be allowed.


> Add key to CMIS exceptions
> --------------------------
>
>                 Key: CMIS-795
>                 URL: https://issues.oasis-open.org/browse/CMIS-795
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: Florian Mueller
>
> CMIS extensions consist of a type and a message. The type is fairly coarse grained. For example, there can be many reasons for a constraint exception. 
> CMIS exceptions should get a third detail; something like a key that identifies the problem more precisely. Some of the values can be defined in the spec, but implementation specific values should also be allowed.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)