春季启动时将实体映射到DTO时的循环依赖性

如何解决春季启动时将实体映射到DTO时的循环依赖性

我有两个实体类:

@Data
@Entity
@Table(name="Foo",schema="REF_DATA")
public class Foo {
 private Long fooId;
 private String fooName;
  @OneToMany(mappedBy="foo")
  @ToString.Exclude
 private List<Bar> bars;
}

@Data
@Entity
@Table(name="Bar",schema="REF_DATA")
public class Bar  {
    private Long barId;
    private String barName;
    @ManyToOne
    @JoinColumn(name="fooId")
    private Foo foo;
}

它们各自的DTO如下:

public class FooDto {
 private Long fooId;
 private String fooName;
 @JsonIgnoreProperties("foo")
 private List<BarDto> bars;
}

public class BarDto  {
    private Long barId;
    private String barName;
    @JsonIgnoreProperties("bars") //added to avoid the cyclic dependency
    private FooDto foo;
}

当用户致电/getAllData时,我们将返回以下DTO:

public class FooBar {
    List<FooDto> foo;
    List<BarDto> bars;
}

我们能够使用JPA从后端获取数据,但是在将Entity映射到Dto时遇到错误。映射器代码如下:

public interface DomainToDtoMapper<E extends BaseEntity,D extends BaseDto> {

   D mapDomainToDto(E domain);
}

public class FooDomainToDtoMapper implements DomainToDtoMapper<Foo,FooDto> {
    @Override
    public FooDto mapDomainToDto(Foo domain) {
        FooDto fooDto = new FooDto();
        FooDto.setfooId(domain.getfooId());
        FooDto.setfooName(domain.getfooName());
        if (domain.getBars() != null) {
            BarDomainToDtoMapper barDomainToDtoMapper= new BarDomainToDtoMapper();
            fooDto.setBars(domain.getBars().stream()
                    .map(barDomainToDtoMapper::mapDomainToDto)
                    .collect(Collectors.toList()));
        }
        return fooDto;
    }

}


public class BarDomainToDtoMapper implements DomainToDtoMapper<Bar,BarDto> {
    @Override
    public BarDto mapDomainToDto(Bar domain) {
        BarDto barDto = new BarDto();
        barDto.setBarId(domain.getBarId());
        barDto.setBarName(domain.getBarName());
        //works fine if we remove this If condition but Bar won't have Foo in final output
        if (domain.getFoo() != null) {
            FooDomainToDtoMapper fooDomainToDtoMapper= new FooDomainToDtoMapper();
            barDto.setFoo(domain.getFoo());
        }
        return barDto ;
    }

}

Bar映射到BarDto时,我们遇到了StackOverflow错误。

org.springframework.web.util.NestedServletException: Handler dispatch failed; nested exception is java.lang.StackOverflowError
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1055) ~[spring-webmvc-5.2.8.RELEASE.jar:5.2.8.RELEASE]
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943) ~[spring-webmvc-5.2.8.RELEASE.jar:5.2.8.RELEASE]
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) [spring-webmvc-5.2.8.RELEASE.jar:5.2.8.RELEASE]
    at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) [spring-webmvc-5.2.8.RELEASE.jar:5.2.8.RELEASE]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:626) [tomcat-embed-core-9.0.37.jar:4.0.FR]
    at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) [spring-webmvc-5.2.8.RELEASE.jar:5.2.8.RELEASE]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) [tomcat-embed-core-9.0.37.jar:4.0.FR]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat-embed-core-9.0.37.jar:9.0.37]

Caused by: java.lang.StackOverflowError: null
    at com.jpmorgan.markets.dto.mapper.FooDomainToDtoMapper .mapDomainToDto(FooDomainToDtoMapper .java:17) ~[classes/:na]
    at com.jpmorgan.markets.dto.mapper.BarDomainToDtoMapper .mapDomainToDto(BarDomainToDtoMapper .java:23) ~[classes/:na]
    at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[na:1.8.0_231]
    at java.util.Iterator.forEachRemaining(Iterator.java:116) ~[na:1.8.0_231]
    at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) ~[na:1.8.0_231]
    at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) ~[na:1.8.0_231]
    at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) ~[na:1.8.0_231]
    at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) ~[na:1.8.0_231]
    at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[na:1.8.0_231]
    at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) ~[na:1.8.0_231]

类似地,如果用户按ID要求返回个人BarDtoFooDto,我们希望返回它们。但问题是,在最终输出中,一个对象必须包含另一个对象。我尝试在实体中添加@JsonBackReference@JsonManagedReference,但仍然遇到相同的错误。是否因为我们将实体显式映射到DTO而不是直接返回实体?不用使用Mapstruct之类的方法,还有其他更好的方法吗?

解决方法

您需要使用下面的代码中的@JsonBackReference@JsonManagedReference

Foo实体

@Data
@Entity
@Table(name="Foo",schema="REF_DATA")
public class Foo {
   private Long fooId;
   private String fooName;
   @OneToMany(mappedBy="foo")
   @ToString.Exclude
   @JsonManagedReference
   private List<Bar> bars;
}

酒吧实体

@Data
@Entity
@Table(name="Bar",schema="REF_DATA")
public class Bar  {
    private Long barId;
    private String barName;
    @ManyToOne
    @JoinColumn(name="fooId")
    @JsonBackReference
    private Foo foo;
}

*注意:如果仍然遇到任何问题,请尝试从@JsonManagedReference实体中删除Foo

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-