Spring data rest pitfalls? Did someone in production decisions?

Does anyone have experience of using spring data rest in a real job? How convenient then to implement the frontend under this implementation of Angular/Vaadin?
July 8th 19 at 11:36
1 answer
July 8th 19 at 11:38
Solution
Overall a handy thing, if you do not want the implementation of some complex business logic, then Spring Data REST is enough. Plus out of the box there is a filter, paginate and even support for HATEOAS. Problems in the interaction with the frontend Angular/Vaadin was not observed.
Then the question in the subject. Example: is the substance of the reporting period. Pluggable Spring Data Rest and have the opportunity to read to edit this entity. Now you need to add a separate method Closure period. Accordingly create Servi and there is implemented this method. Question as a reference to that method feed in Spring Data Rest? - mary.Bosco27 commented on July 8th 19 at 11:41
: Easy, you need to override the handler: docs.spring.io/spring-data/rest/docs/current/refer... - hank51 commented on July 8th 19 at 11:44
Thank you so much. I will try - mary.Bosco27 commented on July 8th 19 at 11:47

Find more questions by tags JavaSpring