|
If you were logged in you would be able to see more operations.
|
|
|
| Proposal: |
We should change delete attempts on the root folder and checkIn to throw "ConstraintViolationException" in those cases.
This would make OperationNotSupportedException specific to optional capabilities, and constraintViolation specific to constraints of the CMIS domain model.
We should change delete attempts on the root folder and checkIn to throw "ConstraintViolationException" in those cases.
This would make OperationNotSupportedException specific to optional capabilities, and constraintViolation specific to constraints of the CMIS domain model.
|
| Resolution: |
Proposal accepted.
|
|
Currently in the CMIS spec, we're a bit inconsistent about when to use "OperationNotSupportedException" vs. "ConstraintViolationException".
For example:
We said in the spec that OperationNotSupportedException is supposed to be about optional capabilities, and we usually use it that way... but we also throw it when:
- You try to check in an object that is not checked out.
- You try to delete the root folder.
|
|
Description
|
Currently in the CMIS spec, we're a bit inconsistent about when to use "OperationNotSupportedException" vs. "ConstraintViolationException".
For example:
We said in the spec that OperationNotSupportedException is supposed to be about optional capabilities, and we usually use it that way... but we also throw it when:
- You try to check in an object that is not checked out.
- You try to delete the root folder. |
Show » |
|
Bug
Closed
Minor
Make use of "OperationNotSupported" vs. "ConstraintViolationException" more consistent