The annotation is needed to reduce method quantity.īut there is a complicated moment with Spring bean injection into aspect. I've written an aspect to interact with all the calls for getter methods with my custom annotation. The Proxy example is somehow applicable to dynamic query parameters and dynamic headers but the Wrapper example not so much.We have to write boilerplate code inside our wrapper.It requires modifying the controller code and this is redundant cause we have a lot of Spring and Jackson code from above.Like when UnitRequest has a field SubUnit. It will take many more lines of code to proxy the value of the internal composite fields.We can take inside a library three classes from the proxy example.We could not write boilerplate code for field values verification. The Proxy solution looks interesting for reusable cases.We have only one additional line inside the controller.There are a lot of questions and discussions about it ĭefault values for request parameters and request ( defaultValue = "19" ) Integer age, ( defaultValue = "John Snow" ) String nameĭynamic values for request parameters and request ( defaultValue = "$ How to make dynamic Spring default values for composite objects input into a REST controller? There are a lot of written Spring REST API services with a lot of common code lines like converters, formatters, custom marshallers, etc. But it's still important to describe your path for the future researcher. And I fail sometimes within my researches of the best solution like many developers. I used to look for common solutions for the problems I face.
0 kommentar(er)
