为什么从Spring Framework 5.x中放弃对Jasper的支持? [英] Why was Jasper support dropped out from Spring Framework 5.x?

问题描述

根据我们的项目报告功能，我们一直在使用Jasper和Spring Boot，但根据

We have been using Jasper with Spring Boot for our project's reporting feature but according to the Spring Framework 5.x release documentation Jasper support has been dropped out.

• 我可以知道为什么这样做吗?

如果我们需要Jasper支持，他们建议保留使用Spring Framework4.3.x.

They have recommended to stay on Spring Framework 4.3.x in case we need Jasper support.

• 如果我们想升级到Spring Framework 5.x并仍然使用Jasper，该怎么办?

推荐答案

Both parts of your question are answered in the JIRA ticket that tracked the support being dropped.

我可以知道为什么这样做吗?

May I know why this has been done?

经过一番调查，JasperReports中新的Exporter API被设计为以ExporterInput/ExporterOutput对象的形式进行前期配置，而不适合Spring的JasperReports视图类层次结构中的零碎方法，特别是通常不采用声明式配置样式用在那里.除此之外，由于整个JasperReports配置模型的API发生了广泛的变化，我们不得不以一种严重不兼容的方式重新设计整个JasperReports视图支持.

After some investigation, the new Exporter API in JasperReports is designed for upfront configuration in the form of ExporterInput / ExporterOutput objects, not lending itself to the piecemeal approach in Spring's JasperReports view class hierarchy and in particular not to the declarative configuration style typically used there. Even aside from that, we'd have to redesign our entire JasperReports view support in an severely incompatible way, due to the wide-ranging API changes across the JasperReports configuration model.

如果我们想升级到Spring Framework 5.x并仍然使用Jasper，该怎么办?

What if we want to upgrade to Spring Framework 5.x and still use Jasper, is there any alternative for doing so?

因此，我们建议在Spring MVC处理程序方法中本地使用JasperReports API，从而从专门设计的RESTful端点生成报告.

As a consequence, we rather recommend native use of the JasperReports API in Spring MVC handler methods, generating reports from specifically designed RESTful endpoints.

这篇关于为什么从Spring Framework 5.x中放弃对Jasper的支持?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！