Spring Boot POST接口返回500错误 invoiceRepository空指针排查

Spring Boot应用开发POST接口，Postman调用/invoice/save路径返回500 Internal Server Error，后台报错信息：

Cannot invoke "com.example.invoices.repository.IInvoiceRepository.save(Object)" because "this.invoiceRepository" is null

报错核心原因是Spring依赖注入失效，InvoiceService类中的invoiceRepository没有被IoC容器赋值为可用的Repository实例，调用save方法时触发空指针，具体触发场景通常为以下几种：

• InvoiceService类未添加@Service注解，没有被Spring识别为业务层Bean纳入容器管理范围，类内部的依赖不会被自动注入
• InvoiceService添加了@Service注解，但invoiceRepository字段没有通过注解/构造函数配置注入规则，Spring无法完成Repository实例的装配
• Controller层的invoiceService实例是手动通过new关键字创建的，手动实例化的对象不受Spring容器管控，内部依赖自然保持null值
• 额外隐患：当前Invoice实体类仅定义了带3个参数的有参构造，缺少JPA要求的无参构造，即使解决了空指针问题，后续持久化操作也会抛出实体实例化异常

按以下步骤逐一检查修复：

1. 修正Service层代码，添加@Service注解，使用构造函数注入Repository依赖（Spring 4.3+单构造函数场景无需额外加@Autowired）：

@Service
public class InvoiceService {
    private final IInvoiceRepository invoiceRepository;

    // 构造注入，Spring自动传入IInvoiceRepository实例
    public InvoiceService(IInvoiceRepository invoiceRepository) {
        this.invoiceRepository = invoiceRepository;
    }

    @Transactional
    public Invoice saveInvoice(Invoice invoice) {
        return invoiceRepository.save(invoice);
    }
}

2. 修正Controller层代码，确保invoiceService通过Spring注入获取，不要手动new实例，同时补全类上的请求路径映射（匹配调用的/invoice/save路径）：

@RestController
@RequestMapping("/invoice")
public class InvoiceController {
    private final InvoiceService invoiceService;

    // 构造注入Service实例
    public InvoiceController(InvoiceService invoiceService) {
        this.invoiceService = invoiceService;
    }

    @PostMapping("/save")
    public ResponseEntity<Invoice> addInvoice(@RequestBody InvoiceDTO invoice) {
        try {
            Invoice newInvoice = invoiceService.saveInvoice(
                    new Invoice(invoice.getSerialNumber(), invoice.getStatus(), invoice.getCreatedDate())
            );
            return new ResponseEntity<>(newInvoice, HttpStatus.CREATED);
        } catch (Exception e) {
            // 开发阶段建议打印异常栈，不要直接吞异常方便排查问题
            e.printStackTrace();
            return new ResponseEntity<>(null, HttpStatus.INTERNAL_SERVER_ERROR);
        }
    }
}

3. 给Invoice实体类补充无参构造函数，满足JPA实体的实例化要求：

@Entity
@Table(name = "invoice")
public class Invoice {
    // 省略原有字段、有参构造、getter/setter方法

    // 补充JPA需要的无参构造
    public Invoice() {
    }
}

修复完成后重启Spring Boot应用，重新通过Postman发起POST请求，空指针异常会消失，接口可以正常执行发票数据持久化逻辑。

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