/rest/object - POST not returning the entity persisted about spring-data-rest HOT 6 CLOSED

Actually the spec says that a POST should "contain an entity which describes the status of the request and refers to the new resource, and a Location header". Since there's no standard way to "describe the status of the request" using JSON, I opted to not try and include an entity in the response and simply use the Location header to point to the URL of the new resource.

If it's more convenient to return the newly-saved resource, then it wouldn't be that hard to do. IMO it's one of those gray areas where different server implementations create different expectations. My original thought was to save the bandwidth and not send a response entity back on POST because the user agent only needs to know if the save succeeded and the ID of the entity is the URI sent in the Location header.

from spring-data-rest.

Hin Jon,
okay got that. My expectations was, as you already mentioned, based on previous work with other implementations. The thing is, if I get 201 and the location to the object, that I won't try to merge the location into the object persisted and start another roundtrip getting the "whole" entity anyway.

But as you said, that is a matter of taste.

from spring-data-rest.

Riak has this behaviour but allows you to put a query parameter of "returnBody=true", which will return the entity you just created.

Would something like this work for you?

from spring-data-rest.

Jon,
I think this would be a solid way to go.

Great!

from spring-data-rest.

Just pushed a change (commit df8a891) to the POST method (of the entity, not of the relation/property POST) that accepts a query parameter of "returnBody=true" to return the JSON of the saved entity on a POST. By default, the behaviour is the same as currently (no body at all). Setting this query parameter to true will cause the entity to be rendered into the response, so you'll get a 201 and the entity representation.

from spring-data-rest.

Great!

from spring-data-rest.