POST to Children resource is confusing

XMLWordPrintable

    • Type: Bug
    • Resolution: Applied
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: REST/AtomPub Binding
    • None
    • Hide

      POST to Children is for create. Ids and ObjectIds in the posted document (if any) are ignored.
      Create a Move resource with a POST method. The resource identifies the destination folder, the POST should contain the Id or ObjectId of the resource to be moved (i.e. could be an Entry document with everything except id ignored, or just an xml subgroup like atom:id or something similar).

      Show
      POST to Children is for create. Ids and ObjectIds in the posted document (if any) are ignored. Create a Move resource with a POST method. The resource identifies the destination folder, the POST should contain the Id or ObjectId of the resource to be moved (i.e. could be an Entry document with everything except id ignored, or just an xml subgroup like atom:id or something similar).

      Perhaps these are several issues, but all related to posting to the children resource:

      1. How to distinguish between create and move?
      2. If create, what to do with id in the posted entry? (ignore? error?)
      3. If create, what to do if path in entry dosn't match the resource's folder? (error? ignore?)
      4. If move, all you really need is a from identity and a destination folder identity (the resource). What to do with the rest of the posted entry? (ignore? updateProperties? assert that they are correct? exception if present?)

            Assignee:
            Al Brown (Inactive)
            Reporter:
            Ryan McVeigh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: