Spring Hateoas/HAL序列化异常：GET请求返回正常却抛警告

Hey there, let's break down and fix your two issues step by step—first that annoying Jackson serialization warning, then those extra null fields cluttering up your links.

1. Resolving the Jackson Serialization Warning #

What's causing it? #

The warning pops up because of a conflict between two Jackson modules:

• Jackson2HalModule from Spring HATEOAS (handles serialization of ResourceSupport's links in HAL format)
• PersistentEntityJacksonModule from Spring Data REST (manages serialization of persistent entities like your Cpu class annotated with @Document)

Since your ComputerComponent abstract class extends ResourceSupport AND your Cpu is a Spring Data persistent entity, both modules try to take control of serializing the links field—leading to the "Cannot override _serializer" error.

How to fix it #

The cleanest solution is to separate your persistent entities from HATEOAS response objects. Here's how:

Step 1: Remove ResourceSupport inheritance from your entity classes

Update your abstract parent class to be a plain persistent entity, no HATEOAS inheritance:

@Getter @Setter 
@JsonAutoDetect(fieldVisibility = JsonAutoDetect.Visibility.ANY) 
public abstract class ComputerComponent { 
    // Keep all your existing fields (componentType, producent, model, etc.)
    // Remove the ResourceSupport inheritance
}

Step 2: Create a dedicated HATEOAS response DTO

Make a new class that extends ResourceSupport to hold your entity data plus links:

@Getter @Setter
public class ComponentResponse extends ResourceSupport {
    // Copy all fields from ComputerComponent you need in the response
    private String componentType;
    private String producent;
    private String model;
    // Add entity-specific fields (e.g., for Cpu)
    private long productId;
    private CpuParameters cpuParameters;
}

Step 3: Modify your controller to convert entities to DTOs

In your controller, fetch the entity, map it to the response DTO, then add your links:

@GetMapping(value = "/{id}", produces = "application/json; charset=UTF-8")
@ResponseStatus(HttpStatus.OK)
public ComponentResponse getComponent(@PathVariable("component") String component, @PathVariable("id") long id) {
    ComputerComponent computerComponent = repositoryProvider.findComponent(component, id);
    if (computerComponent == null) throw new ComponentNotFoundException(component, id);
    
    // Map entity to DTO (use BeanUtils or a mapper like MapStruct for cleaner code)
    ComponentResponse response = new ComponentResponse();
    BeanUtils.copyProperties(computerComponent, response);
    
    // Add HATEOAS links to the DTO
    response.add(linkTo(methodOn(ComponentsController.class)
            .getComponent(component, id)).withSelfRel());
    response.add(linkTo(methodOn(ComponentsController.class)
            .getListOfComponents(computerComponent.getComponentType().toString()))
            .withRel("collection"));
    
    return response;
}

This way, your persistent entities stay focused on database logic, and the DTO handles HATEOAS—eliminating the module conflict entirely.

2. Removing Null Fields from HATEOAS Links #

Why those null fields exist #

The Link class from Spring HATEOAS includes optional properties like hreflang, media, title, etc. By default, Jackson serializes all fields of an object—even if they're null. That's why you're seeing those empty values in your JSON.

How to fix it #

You can configure Jackson globally to ignore null fields in all responses. Here are two easy ways:

Option 1: Use application.properties

Add this line to your application.properties file:

spring.jackson.default-property-inclusion=non_null

Option 2: Configure via Java Config

If you prefer Java-based configuration, create a Jackson config class:

@Configuration
public class JacksonConfiguration {
    @Bean
    public ObjectMapper objectMapper() {
        ObjectMapper objectMapper = new ObjectMapper();
        // Only include non-null fields in serialization
        objectMapper.setSerializationInclusion(JsonInclude.Include.NON_NULL);
        return objectMapper;
    }
}

Either approach will strip out all null fields from your JSON response, leaving only the relevant rel and href fields in your links.

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