Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Proposal:
      Hide

      REST does not support returning documentId

      Show
      REST does not support returning documentId

      Description

      How should this info be reflected in AtomPub?

      Options:
      1. Location Header - Where does this go? The documentId whould be mapped to Atom Entry. It seems very weird that on a delete of a content stream, the server redirects the client to the atom entry
      2. New CMIS-specific header. E.g., CMIS-ObjectId: <id>. However this was not a good option earlier. Maybe that has changed.

      This items needs to be resolved before 274 can be reflected

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              albertcbrown Al Brown (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: