@haulmont-git commented on Wed Dec 13 2017

Exposing services in REST have many limitations such as:

• inability to work with files,
• inability to work with headers (send redirect, send custom error status, etc.),
• unobvious serialization behavior and customization,
• ... more to come.

According to feedback, developers usually end up with creating custom Spring REST Controllers:

https://www.cuba-platform.com/discuss/t/there-is-a-way-to-generate-html-from-a-rest-api-call/3185/2
https://www.cuba-platform.com/discuss/t/how-to-restrict-rest-api-v2-to-allow-post-only/3166

So instead of reinventing spring-mvc within our REST services maybe we need to enhance custom controllers usage, here are some ideas on it:

• Easier way to create controllers in REST context.
  ** Current configuration is quite [https://doc.cuba-platform.com/manual-6.4/rest_api_v2_custom_controllers.html verbose].
  ** Support creation from Studio.
• Provide the same (unified) serialization across generic REST and Custom controllers.
• Consider to remove REST out of the WEB module (portal?)

Original issue: https://youtrack.haulmont.com/issue/PL-10144