getDescendants method -- mis-match between Schemas & Domain model

XMLWordPrintable

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

      We should REMOVE both properties from the schema/domain model.

      IIRC, we already agreed to remove them anyway... but we should complete that change.

      Show
      We should REMOVE both properties from the schema/domain model. IIRC, we already agreed to remove them anyway... but we should complete that change.
    • Hide

      We believe this is a dupe. Ethan to verify.

      Show
      We believe this is a dupe. Ethan to verify.

      Currently, the CMIS schema & domain model are inconsistent in the following ways for the definition of the "getDescendants" method.

      Inputs:

      • includeRelationships:
        • Domain model says: It's an enum with values "source", "target", "both", "none" (default)
        • Schemas say its a boolean.

      (Note: includeRelationships is also defined this way for getChildren,getFolderParent, getObjectParents, getCheckedoutDocs, getProperties).

      • orderBy:
        • Domain model says it's a string that is a valid "ORDER BY" statement in CMIS-SQL (just like query).
        • Schemas don't include it.

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

              Created:
              Updated: