Unimplemented http methods now set a 405 status
create, delete, get, getList and update method shouldn't be abstract …
Since no method is mandatory in REST, AbstractRestfulController shouldn't force to implement these methods (create, delete, get, getList and update) thus conducing to a concrete class with empty/unused methods.
unimplemented http methods set a 405 status
Please add in unit tests to verify the behavior.
My bad, should have done that.
Added unit test for unimplemented methods
Removed no longer complient test
Great idea -- wish I'd thought of this before!
Merge pull request #4808 from qapa/#4564
Merge branch 'hotfix/4808' into develop
Forward port #4808
It looks better, but stated in rfc regarding 405 status: "...The response MUST include an Allow header containing a list of valid methods for the requested resource."
It's for that reason I use 501 (not implemented) because I don't have to return anything (SHOULD) while with 405 I MUST return something, although 501 is not perfect too (it's saying method not implemented for any resources).