Why JSON is used for calls between interfaces, how fastjson is assigned, fastjson 1.2 [email protected] Mapping relatio

Why should calls between interfaces use json？

Interaction between applications , Unlike the interaction between front and back , Then it is convenient to define and name consistently , Because in normal development , It may be an interface written by multiple teams to access each other , Therefore, the parameter names passed by the receiver and the sender in the development process may not be exactly the same , therefore , You simply define an object to receive , If the names don't match , You will not get value .

If this situation is found during joint commissioning , Then change the field , Dependencies that may involve multiple files , It's a lot of trouble .

Therefore, see interactive use json To receive data .

fastjson How do you assign values ？

adopt @JSONField, The fields of the interface message can be mapped to @JSONField name Specified fields .

Then go through set Method to assign a value to your corresponding java bean attribute , So this is why you need to provide corresponding java bean Of set Method , And is public Why .

fastjson The latest version 1.2.83 Message and @JSONField Mapping relationship problem

1.2.83 Result table （1.2.70 All normal values ）

message	@JSONField	Conversion result
“appId”:“app_id”,	@JSONField(name = “app_id”)	The value is null
“app_id2”:“app_id2”	@JSONField(name = “appId2”)	Normal value
“op_id”:“op_id”,	//bean Relationship ①： Hump reception @JSONField(name = “op_id”) private String opId;	Normal value
“op_id1”:“op_id1”,	//bean Relationship ②： Original value receiving @JSONField(name = “op_id1”) private String op_id1;	Normal value
“op_id2”:“op_id2”,	//bean Relationship ③： It is worth receiving @JSONField(name = “op_id2”) private String param;	Normal value

Json message

{
    
    "op_id":"op_id",
    "op_id1":"op_id1",
    "op_id2":"op_id2",
    "appId":"app_id",
    "app_id2":"app_id2"
}

Bean

@Data
public class Json1 {
    

    /** * json Message and @JSONField Agreement  */
    //bean Relationship ①： Hump reception 
    @JSONField(name = "op_id")
    private String opId;
    //bean Relationship ②： Original value receiving 
    @JSONField(name = "op_id1")
    private String op_id1;
    //bean Relationship ③： It is worth receiving 
    @JSONField(name = "op_id2")
    private String param;

    /** * json Message transmission @JSONField Hump switching  */
    @JSONField(name = "app_id")
    private String app_id;
    @JSONField(name = "appId2")
    private String appId2;
}

Controller

package com.example.helloworld.controller;

import com.alibaba.fastjson.JSON;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.data.redis.core.StringRedisTemplate;
import org.springframework.http.MediaType;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class HelloController {
    

    @RequestMapping("/hello")
    public String hello() {
    
        return "hello ==== " + 222;
    }

    @RequestMapping(value = "/json1", method = RequestMethod.POST, produces = MediaType.APPLICATION_JSON_UTF8_VALUE, consumes = MediaType.APPLICATION_JSON_UTF8_VALUE)
    public Json1 json1(@RequestBody Json1 json) {
    
        System.out.println(json);
        return json;
    }

    /** *  Why requestJson Pick up ? I don't want to be with you bane The attribute is called the same , I also don't want to change , What do I do ? * @param requestJson * @return */
    @RequestMapping(value = "/json2", method = RequestMethod.POST, produces = MediaType.APPLICATION_JSON_UTF8_VALUE, consumes = MediaType.APPLICATION_JSON_UTF8_VALUE)
    public Json1 json1(@RequestBody String requestJson) {
    
        System.out.println("request json:" + requestJson);
        Json1 json1 = JSON.parseObject(requestJson, Json1.class);
        System.out.println(json1);
        return json1;
    }
}

Output results

1.2.70

request json:{
    
    "op_id":"op_id",
    "op_id1":"op_id1",
    "op_id2":"op_id2",
    "appId":"app_id",
    "app_id2":"app_id2"
}
Json1(opId=op_id, op_id1=op_id1, param=op_id2, app_id=app_id, appId2=app_id2)

1.2.83

request json:{
    
    "op_id":"op_id",
    "op_id1":"op_id1",
    "op_id2":"op_id2",
    "appId":"app_id",
    "app_id2":"app_id2"
}
Json1(opId=op_id, op_id1=op_id1, param=op_id2, app_id=null, appId2=app_id2)

postman Set transmission json test

Source code address ：https://gitlab.com/publicstudy/helloworld