[FIXED] Spring Boot using Json as request parameters instead of an entity/model

Issue

Our company is planning to switch our microservice technology to Spring Boot. As an initiative I did some advanced reading and noting down its potential impact and syntax equivalents. I also started porting the smallest service we had as a side project.

One issue that blocked my progress was trying to convert our Json request/response exchange to Spring Boot.

Here's an example of the code: (This is Nutz framework for those who don't recognize this)

@POST
@At // These two lines are equivalent to @PostMapping("/create")
@AdaptBy(type=JsonAdapter.class)
public Object create(@Param("param_1") String param1, @Param("param_2) int param2) {
    MyModel1 myModel1 = new MyModel1(param1);
    MyModel2 myModel2 = new MyModel2(param2);
    myRepository1.create(myMode12);
    myRepository2.create(myModel2);
    return new MyJsonResponse();
}

On PostMan or any other REST client I simply pass POST:

{
    "param_1" : "test",
    "param_2" : 1
}

I got as far as doing this in Spring Boot:

@PostMapping("/create")
public Object create(@RequestParam("param_1") String param1, @RequestParam("param_2) int param2) {
    MyModel1 myModel1 = new MyModel1(param1);
    MyModel2 myModel2 = new MyModel2(param2);
    myRepository1.create(myMode12);
    myRepository2.create(myModel2);
    return new MyJsonResponse();
} 

I am not sure how to do something similar as JsonAdapter here. Spring doesn't recognize the data I passed.

I tried this but based on the examples it expects the Json paramters to be of an Entity's form.

@RequestMapping(path="/wallet", consumes="application/json", produces="application/json")

But I only got it to work if I do something like this:

public Object (@RequestBody MyModel1 model1) {}

My issue with this is that MyModel1 may not necessarily contain the fields/parameters that my json data has.

The very useful thing about Nutz is that if I removed JsonAdapter it behaves like a regular form request endpoint in spring.

I couldn't find an answer here in Stack or if possible I'm calling it differently than what existing spring devs call it.

Our bosses expect us (unrealistically) to implement these changes without forcing front-end developers to adjust to these changes. (Autonomy and all that jazz). If this is unavoidable what would be the sensible explanation for this?

Solution

In that case you can use Map class to read input json, like

@PostMapping("/create")
public Object create(@RequestBody Map<String, ?> input) {
     sout(input.get("param1")) // cast to String, int, ..
}

Answered By - sagarr
Answer Checked By - David Marino (JavaFixing Volunteer)