RE: [cmis-comment] Better exception mapping

[<Choy_David@emc.com>]

Thank you for proposing to have more explicit status code/status message
mapping.
This will certainly help an interoperable client.
The TC, however, decided to defer making such change until V2, partially
because V2 will accommodate more use cases which may give us a broader
context to define explicit mapping.
We thank you for your support of CMIS, and hope this deferral is
acceptable.

Regards,
David

-----Original Message-----
From: Jeff Potts [mailto:jpotts@optaros.com] 
Sent: Thursday, December 10, 2009 4:36 PM
To: cmis-comment@lists.oasis-open.org
Subject: [cmis-comment] Better exception mapping

Regarding the exception handling in 3.2.4.1 Common CMIS Exceptions, I
think we need better (more explicit?) status code/status message mapping
here. The way it currently stands, a client app has no way of knowing
the difference between a contentAlreadyExists (409) error and a
versioning (also 409) error. People writing to a specific client can
look at the error message to decide but that doesn't work for an
interoperable client that can't predict the content of those messages.

Jeff
-- 
This publicly archived list offers a means to provide input to the
OASIS Content Management Interoperability Services (CMIS) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: cmis-comment-subscribe@lists.oasis-open.org
Unsubscribe: cmis-comment-unsubscribe@lists.oasis-open.org
List help: cmis-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/cmis-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis