Spring Boot 2.x中Spring层按URL动态转换JSON至指定实体类

针对你的需求，我们可以通过Spring MVC自定义参数解析器实现请求URL到实体类型的映射转换，完全在Spring层面处理，无需修改Jackson/Gson的全局配置，具体步骤如下：

1. 实现URL-实体类型映射注册表 #

先把URL到目标类型的映射封装成Spring Bean，方便后续获取：

@Component
public class EntityTypeRegistry {
    private final Map<String, Class<?>> urlTypeMap = new ConcurrentHashMap<>();

    // 初始化映射关系，可根据实际需求调整
    @PostConstruct
    public void initRegistry() {
        urlTypeMap.put("/sea/user", User.class);
        urlTypeMap.put("/sea/car", Car.class);
        // 添加其他URL与实体类的映射
    }

    public Class<?> getTargetType(String requestUrl) {
        return urlTypeMap.get(requestUrl);
    }
}

2. 自定义参数解析器 #

创建HandlerMethodArgumentResolver实现类，负责解析SEACreateRequest参数，核心逻辑是根据请求URL从注册表获取目标类型，将Jackson解析后的Map列表转换为对应实体类实例：

@Component
public class SEACreateRequestArgumentResolver implements HandlerMethodArgumentResolver {

    private final ObjectMapper objectMapper;
    private final EntityTypeRegistry typeRegistry;

    // 注入Spring容器中的ObjectMapper和类型注册表
    public SEACreateRequestArgumentResolver(ObjectMapper objectMapper, EntityTypeRegistry typeRegistry) {
        this.objectMapper = objectMapper;
        this.typeRegistry = typeRegistry;
    }

    // 判断当前参数是否需要该解析器处理
    @Override
    public boolean supportsParameter(MethodParameter parameter) {
        return SEACreateRequest.class.isAssignableFrom(parameter.getParameterType());
    }

    // 参数解析核心逻辑
    @Override
    public Object resolveArgument(MethodParameter parameter, ModelAndViewContainer mavContainer,
                                  NativeWebRequest webRequest, WebDataBinderFactory binderFactory) throws Exception {
        // 获取当前请求的URL
        HttpServletRequest request = webRequest.getNativeRequest(HttpServletRequest.class);
        assert request != null;
        String requestUri = request.getRequestURI();

        // 从注册表获取目标实体类型
        Class<?> targetType = typeRegistry.getTargetType(requestUri);
        if (targetType == null) {
            throw new IllegalArgumentException("Unsupported request URL: " + requestUri);
        }

        // 读取请求体并解析为临时Map结构
        String requestBody = StreamUtils.copyToString(request.getInputStream(), StandardCharsets.UTF_8);
        Map<String, Object> tempRequestMap = objectMapper.readValue(requestBody, new TypeReference<>() {});
        List<Map<String, Object>> entityMaps = (List<Map<String, Object>>) tempRequestMap.get("entities");

        // 将Map列表转换为目标实体类列表
        List<Object> targetEntities = entityMaps.stream()
                .map(entityMap -> objectMapper.convertValue(entityMap, targetType))
                .collect(Collectors.toList());

        // 封装为SEACreateRequest对象
        SEACreateRequest seaRequest = new SEACreateRequest();
        seaRequest.setEntities(targetEntities);
        // 如果SEARequest父类有其他字段，需在此从tempRequestMap中读取并设置

        return seaRequest;
    }
}

3. 注册自定义解析器 #

将自定义解析器注册到Spring MVC配置中，确保Spring优先使用该解析器处理SEACreateRequest参数：

@Configuration
public class WebMvcConfig implements WebMvcConfigurer {

    private final SEACreateRequestArgumentResolver requestResolver;

    public WebMvcConfig(SEACreateRequestArgumentResolver requestResolver) {
        this.requestResolver = requestResolver;
    }

    @Override
    public void addArgumentResolvers(List<HandlerMethodArgumentResolver> resolvers) {
        // 插入到列表头部，保证优先级高于默认解析器
        resolvers.add(0, requestResolver);
    }
}

4. Controller中直接使用 #

在Controller方法中直接声明SEACreateRequest参数即可，此时entities列表中的元素已经是对应URL的目标类型：

@RestController
@RequestMapping("/sea")
public class SEAController {

    @PostMapping("/user")
    public ResponseEntity<?> handleUserCreate(SEACreateRequest request) {
        List<User> userList = (List<User>) request.getEntities();
        // 业务逻辑处理
        return ResponseEntity.ok(userList);
    }

    @PostMapping("/car")
    public ResponseEntity<?> handleCarCreate(SEACreateRequest request) {
        List<Car> carList = (List<Car>) request.getEntities();
        // 业务逻辑处理
        return ResponseEntity.ok(carList);
    }
}

关键注意事项 #

• 如果SEARequest父类包含其他字段，需在自定义解析器中补充对应字段的赋值逻辑，从临时Map中读取并设置到SEACreateRequest对象。
• 可根据实际需求调整EntityTypeRegistry的URL匹配逻辑，比如支持模糊匹配（提取URL路径段作为匹配key）。
• 异常处理：可自定义业务异常替换IllegalArgumentException，并通过全局异常处理器统一处理。

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