Make use of "OperationNotSupported" vs. "ConstraintViolationException" more consistent

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: Domain Model
    • None
    • Hide

      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.

      Show
      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.
    • Hide

      Proposal accepted.

      Show
      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.

            Assignee:
            Ethan Gur-esh (Inactive)
            Reporter:
            Ethan Gur-esh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: