Spring Boot外卖应用：单请求关联保存用户与地址的实现问题

错误原因分析 #

你遇到的序列化错误：

Resolved [org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Cannot deserialize value of type com.example.EatMe.model.Address from Array value (tokenJsonToken.START_ARRAY)]

核心问题有三点：

• Spring MVC不支持单个接口方法中使用多个@RequestBody，它只能解析请求体中的一份JSON数据
• 你发送的是JSON数组，但接口期望接收两个独立对象，导致序列化失败
• 先保存地址再保存用户的逻辑错误，此时用户ID尚未生成，地址的userId字段无法正确关联

解决方案步骤 #

步骤1：修正实体类的关联关系 #

根据你原本的OneToOne需求，调整实体关联配置，同时支持JPA级联操作：

User实体类修改

@Entity
public class User {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Integer id;
    @Column(nullable = false)
    private String name;
    @Column(nullable = false)
    private String surname;
    @Column(unique = true, nullable = false)
    private String mail;
    @Column(nullable = false)
    private String userType;

    // 替换原有OneToMany为OneToOne，配置级联保存
    @OneToOne(cascade = CascadeType.ALL, orphanRemoval = true)
    @JoinColumn(name = "address_id") // 外键存储在user表，指向address的id
    private Address address;

    // 新增getter/setter
    public Address getAddress() {
        return address;
    }

    public void setAddress(Address address) {
        this.address = address;
    }

    // 原有字段的getter/setter保持不变
}

Address实体类修改

移除手动维护的userId字段，改为双向关联（可选，方便后续查询）：

@Entity
public class Address {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Integer id;
    @Column(nullable = false)
    private String street;
    @Column(nullable = false)
    private Integer streetNumber;
    @Column(nullable = false)
    private Integer postcode;

    // 双向关联，mappedBy指定由User端维护关联关系
    @OneToOne(mappedBy = "address")
    private User user;

    // 新增getter/setter
    public User getUser() {
        return user;
    }

    public void setUser(User user) {
        this.user = user;
    }

    // 原有字段的getter/setter保持不变
}

如果需要保留用户对应多个地址的OneToMany关系，可调整如下：

• User实体：

@OneToMany(cascade = CascadeType.ALL, orphanRemoval = true, mappedBy = "user")
private Set<Address> addresses;

• Address实体：

@ManyToOne
@JoinColumn(name = "user_id")
private User user;

步骤2：恢复Controller的单请求体接收 #

修改UserController，仅接收User对象，地址数据将嵌套在User的JSON中：

@RestController()
@RequestMapping("/api/user")
public class UserController {

    @Autowired
    private UserService userService;
    
    @PostMapping("/add")
    public ResponseEntity<String> addUser(@RequestBody User newUser){
        return userService.addUser(newUser);
    }

    // 其他方法（editMail/deleteUser）保持不变
}

步骤3：修改Service实现级联保存 #

利用JPA的级联特性，保存User时自动关联保存地址：

@Service
public class UserService {
    @Autowired
    private UserRepository userRepository;

    public ResponseEntity<String> addUser(User newUser){
        var userInDB = userRepository.findByMail(newUser.getMail());
        if(userInDB.isPresent()){
            return new ResponseEntity<>("Email is already used.", HttpStatus.BAD_REQUEST);
        }else{
            // 级联保存：保存User时自动保存关联的Address
            userRepository.save(newUser);
            return new ResponseEntity<>("New user and address added.", HttpStatus.OK);
        }
    }

    // 其他方法（setEmail/deleteUser）保持不变
}

步骤4：调整Postman请求的JSON格式 #

根据关联关系发送嵌套JSON：

OneToOne关联请求示例

{
    "name": "Max",
    "surname":"Muster",
    "mail":"test@mail.de",
    "userType":"none",
    "address": {
        "street": "testStreet",
        "streetNumber" : 1,
        "postcode" : 1234
    }
}

OneToMany关联请求示例（多地址）

{
    "name": "Max",
    "surname":"Muster",
    "mail":"test@mail.de",
    "userType":"none",
    "addresses": [
        {
            "street": "testStreet",
            "streetNumber" : 1,
            "postcode" : 1234
        },
        {
            "street": "secondStreet",
            "streetNumber" : 2,
            "postcode" : 5678
        }
    ]
}

关键配置说明 #

• cascade = CascadeType.ALL：指定当保存/更新/删除User时，自动对关联的Address执行相同操作
• orphanRemoval = true：当从User的地址集合中移除某个Address时，自动删除该Address记录
• 无需单独调用AddressService，JPA会自动处理关联数据的持久化

内容的提问来源于stack exchange，提问作者StefanoF02