JPA无cascadeType双向关联无法加载OneToMany子实体问题

技术栈：Spring Data JPA、Lombok，场景为未配置cascadeType的@OneToMany/@ManyToOne双向映射，业务侧需要通过独立Repository维护多端实体，不配置级联操作。

实体定义 #

所有实体继承的公共父类BaseEntity代码：

@SuperBuilder
@Getter
@Setter
@NoArgsConstructor
@MappedSuperclass
@EntityListeners(AuditingEntityListener.class)
public abstract class BaseEntity {

  @Id
  @GeneratedValue
  @Column(columnDefinition = "uuid", updatable = false)
  private UUID id;

  @Version @Builder.Default private long version = 1;
}

双向关联「一」端Company实体代码：

@SuperBuilder
@Getter
@Setter
@ToString(includeFieldNames = true)
@EqualsAndHashCode(callSuper = true)
@NoArgsConstructor
@Entity
@Table(name = "companies")
public class Company extends BaseEntity {

  @ToString.Exclude
  @OneToMany(mappedBy = "company")
  private List<OperatingFacility> operatingFacilities;

}

双向关联「多」端OperatingFacility实体代码：

@SuperBuilder
@Getter
@Setter
@ToString(includeFieldNames = true)
@NoArgsConstructor
@Entity
@Table(name = "operating_facilities")
public class OperatingFacility extends BaseEntity {

  @ToString.Exclude
  @ManyToOne()
  @JoinColumn(name = "company_id")
  private Company company;

}

复现场景 #

测试用例代码：

Company company = companyRepository.save(Company.builder().build());

OperatingFacility operatingFacility =
    operatingFacilityRepository.save(
        OperatingFacility.builder()
            .company(company)
            .build());

final List<OperatingFacility> gotFoundByCompanyId =
    operatingFacilityRepository.findByCompanyId(company.getId());

// 断言通过，数据库层面关联关系存储正常
Assertions.assertEquals(1, gotFoundByCompanyId.size());

Optional<Company> companyOptional = companyRepository.findById(company.getId());
Assertions.assertTrue(companyOptional.isPresent());
Assertions.assertNotNull(companyOptional.get().getOperatingFacilities());

// 断言失败：查询到的Company对象中operatingFacilities集合长度为0
Assertions.assertEquals(1, companyOptional.get().getOperatingFacilities().size());

现象总结：

• 直接通过多端Repository按companyId查询关联数据，可正常返回1条记录，数据库外键关联存储无问题
• 通过一端Repository查询Company实体后，获取到的operatingFacilities集合非null，但长度为0

问题根因 #

cascadeType配置和本次查询异常完全无关，该配置仅控制主实体操作时是否级联操作关联实体，不影响查询逻辑。问题核心原因有两点：

• JPA双向关联不会自动同步两端状态：保存OperatingFacility时仅设置了facility指向company的关联，未将facility加入到company的operatingFacilities集合中。测试场景下默认事务未提交，findById会直接命中一级缓存中初始创建的company对象，该对象的关联集合从未被赋值，返回空集合。
• @OneToMany默认加载策略为FetchType.LAZY，如果查询和保存不在同一个持久化上下文，未显式声明加载关联集合时，返回的懒加载代理集合如果没有触发加载，也可能出现空集合的情况。

解决方案 #

• 1. 双向关联必须主动同步两端状态，推荐在实体中添加专门的关联维护方法，避免漏操作：
     修改Company实体，初始化集合默认值、添加关联维护方法：

@ToString.Exclude
@OneToMany(mappedBy = "company")
@Builder.Default // 保证Lombok构建对象时默认值不丢失
private List<OperatingFacility> operatingFacilities = new ArrayList<>();

// 统一维护双向关联
public void addOperatingFacility(OperatingFacility facility) {
    operatingFacilities.add(facility);
    facility.setCompany(this);
}

保存关联数据时直接调用工具方法即可：

Company company = companyRepository.save(Company.builder().build());
OperatingFacility operatingFacility = new OperatingFacility();
company.addOperatingFacility(operatingFacility);
operatingFacilityRepository.save(operatingFacility);

• 2. 跨持久化上下文查询时，通过join fetch显式加载关联集合，避免全局配置FetchType.EAGER带来的不必要性能损耗，在CompanyRepository中添加自定义查询：

@Query("select c from Company c left join fetch c.operatingFacilities where c.id = :id")
Optional<Company> findByIdWithFacilities(UUID id);

不需要为了解决该问题配置级联，完全可以保留独立Repository管理OperatingFacility的实现方式，不影响正常业务逻辑。

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