Issue Details (XML | Word | Printable)

Key: CMIS-116
Type: Bug Bug
Status: Closed Closed
Resolution: Applied
Priority: Minor Minor
Assignee: Ethan Gur-esh
Reporter: Ethan Gur-esh
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
OASIS Content Management Interoperability Services (CMIS) TC

TypeNotFoundException & notInFolderException -- are these ever still used?

Created: 06/Mar/09 05:21 PM   Updated: 11/Jan/10 07:37 PM
Component/s: Domain Model
Affects Version/s: Draft 0.50
Fix Version/s: Draft 0.62

Proposal:
Get rid of them.


Or at least use them somewhere. :)
Resolution: Proposal accepted.


 Description  « Hide
CMIS domain model & schemas currently include exception types for "notInFolderException" and "typeNotFoundException"... but there's no CMIS service that specifies their use.

IIRC, typeNotFoundException was added to the spec in an early draft version where Object-Types had a different ID than ObjectIDs... but we've since fixed that.

NotInFolder exception may have been used for the multi-filing services... but aren't anymore.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Al Brown added a comment - 04/May/09 12:47 PM
Accepted by TC

Ethan Gur-esh added a comment - 14/May/09 06:23 PM
Removed these two exception types.

Note that I've also moved enumServiceException to CMIS-Core.xsd (and updated the refrence in CMIS-Messaging.xsd)

Al Brown added a comment - 05/Jan/10 12:12 AM
JIRA Cleanup