Community
Participate
Working Groups
When POST /workspace/<workspaceId> is used to create a project, this is the response I got: { "Id": "I", "Location": "http://localhost:8080/workspace/D/I";, "Name": "xcvxcv", "SearchLocation": "http://localhost:8080/solrsearch?wt=json&fl=Id,Name,Length,Directory,LastModified,Location&hl=true&q="; } The location should be "http://localhost:8080/file/I";,
I think "http://localhost:8080/workspace/D/I"; is correct. There are actually two interesting locations here: - The location of the project metadata - The location of the project *contents* They should probably both be included in the response. I had created the ContentLocation header for the second one, but maybe it is missing for POST response. 2.John ArthorneDec 7, 2010 11:02 A.M. I need to think more about this. POST creates both a project and file resource. Deleting the project resource removes that project from the workspace, and deleting the file resource deletes the content. So, these two resources are useful but both resource locations should be included in the POST response.
Some other problems with project creation: - Response has no HTTP "Location" header - Response code is 200 rather than 201 (Created)
Fix released.
