[QPID-6449] [Java Broker] Change REST interfaces to return 422 status code from create/update requests when provided attribute values are invalid or required attributes are missing

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: qpid-java-6.0
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 13/Mar/15 21:43
• Updated: 18/Mar/15 12:12
• Resolved: 18/Mar/15 12:12

Description

At the moment 409 status code is returned for almost every client error.
In order to distinguish validation failures from real conflicts 422 status code can be returned for the former.

422 status code will be returned when invalid attributes values or not all required attributes are provided in REST requests to create or update configured object

The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415(Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the contained instructions. For example, this error condition may occur if an XML request body contains well-formed (i.e., syntactically correct), but semantically erroneous, XML instructions.