Version 3.0.0 (release: 17.10.2024)

You can see the full list of issues with details in the milestones page.

This release has been tested with multiple versions of application servers

• Tomcat9, Tomcat10, Weblogic 14, Weblogic 12, Wildfly 26.1, Glassfish 4.1

and Java versions

• JDK 8, JDK 11, JDK 17, JDK 18

New features

• #146 Upgrade libraries to JasperReports 7.0.1

Bug fixes

• none

Changed behaviour

• Existing reports will break! All existing reports need to be upgraded using JasperReportsStudio 7.0.x first.
  • You can do this with the following steps:
    • select your <report>.jrxml file in the Project Explorer pane
    • right-click on the file or on a directory. If you choose a directory, it will be applied recursively for all .jrxml files in all subdirectories
    • select JasperReports>Update JasperReports files
    • now, the selected .jrxml files will be upgraded to version 7 of JasperReports.
    • then, deploy all modified .jrxml files to the target system, i.e. your application server.
    • you actually don't even need to compile the .jrxml file into an .jasper file for deployment. It will be created automatically if it does not exist. It is safe to delete all .jasper files (if you have the .jrxml file in the directory)
• All other changes are mainly affecting developers, the JasperReports development team changed from using Apache Ant and Apache Ivy to Maven. This makes the development on our side much easier and all artifacts can be taken directly from the Maven repository.
  • Also, using gradle with gretty for testing is currently not working and has been removed from the developer documentation. It is rather advised to test/debug directly from Eclipse.

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
• For running the application on Tomcat10, you have to use jri-3.0.0-jasper-7.0.1-tomcat10.war instead of jri.war.
• Should you run into errors while running the reports, it will be most likely due to not yet upgraded reports to the version 7.x syntax.

Version 2.11.0 (release: 23.11.2023)

You can see the full list of issues with details in the milestones page.

New features

• #136 Upgrade libraries to JasperReports 6.20.6

Bug fixes

• none

Changed behaviour

• none

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
• For running the application on Tomcat10, you have to use jri-2.11.0-jasper-6.20.6-tomcat10.war instead of jri.war.

Version 2.10.1 (release: 17.01.2023)

You can see the full list of issues with details in the milestones page.

It is mainly a maintenance / bugfix release, specifically to support Oracle Weblogic.

New features

• none

Bug fixes

• #123 Constant utl_http.http_version_1_1 causes compiler issues on older Oracle versions
• #126 2 versions of Log4j dependences
• #118 Deploying jri.war file on Oracle Weblogic Server

Changed behaviour

• none

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
• For running the application on Tomcat10, you have to use jri-2.10.1-jasper-6.20.0-tomcat10.war instead of jri.war.

Version 2.10.0 (release: 25.08.2022)

You can see the full list of issues with details in the milestones page.

New features

• #116 JDK 17 LTS Support
• #102 Upgrade to jasperreports-libraries 6.20.0

Bug fixes

• #113 Problem verifying application over HTTPS

Changed behaviour

• none

Deprecated features (still available but will go away eventually)

• none

Obsoleted features (no longer available)

• none

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
• For running the application on Tomcat10, you have to use jri-2.10.0-jasper-6.20.0-tomcat10.war instead of jri.war.

Version 2.9.0 (release: 24.08.2022)

You can see the full list of issues with details in the milestones page.

New features

• #101 PDF encryption (with password), see the section on integration and usage for details.
• #109 ipAddressesAllowed is now available for each data source, not only globally.
• #94 Suppressing debug information on the webpage. By default, the application is more secure. All error messages will be suppressed on the webpage. You can still see them in the server logs. And you can activate it in the application.properties file. The setting is printDebugToScreen in the section [application].
• #102 Upgrade to jasperreports-libraries 6.19.1

Bug fixes

• #111 Unable to generate .csv file. PDF and xlsx work fine bug. Saving (csv and rtf) files on the server did not work.
• #108 Error deploying on Wildfly application server
• #107 Java 11 compatibility => Error de.oc.jasper.ReportUtilities.(ReportUtilities.java:32). The application has been tested with Java 11.

Changed behaviour

• By default, all error messages will be suppressed. You can activate the setting for development environments through the application.properties file. The setting is printDebugToScreen in the section [application].

Deprecated features (still available but will go away eventually)

• none

Obsoleted features (no longer available)

• none

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
• For running the application on Tomcat10, you have to use jri-2.9.0-jasper-6.19.1-tomcat10.war instead of jri.war.

Version 2.8.1 (release: 10.02.2022)

You can see the full list of issues with details in the milestones page.

New features

• none

Bug fixes

• #98 reportsPath: default value and relative paths (../reports or ..\reports) don't work

Changed behaviour

• none

Deprecated features (still available but will go away eventually)

• none

Obsoleted features (no longer available)

• none

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
• For running the application on Tomcat10, you have to use jri-2.8.1-jasper-6.18.1-tomcat10.war instead of jri.war.

Version 2.8.0 (release: 09.02.2022)

You can see the full list of issues with details in the milestones page.

New features

• #93 Upgrading log4j 1.x to log4j 2.x (2.17.1)
• #84 Variable for report path
  • You can now specify a list of report locations like a search path
• #79 XLIB_HTTP.http_version_1_0 was outdated and is upgraded to 1.1 and implemented as an optional parameter. You can downgrade to 1.0 if this is needed.
• #82 Unable to start JRI with tomcat 10. Tomcat changed in release 10 some of the library packages: https://tomcat.apache.org/migration-10.html#Specification_APIs. I will continue to develop using the old packages and create a modified jri.war file just for Tomcat10, e.g. jri-2.8.0-jasper-6.18.1-tomcat10.war.
• #70 Upgrade Oracle JDBC libraries to 21.4.0.0.1
• #90 Upgrade spring boot libraries. For security reasons, we include a higher version of the spring boot libraries.
• #80 Upgrade to JasperReportsLibraries 6.18.1

Bug fixes

• #96 Connection pool error when session is killed on server, now reconnects gracefully
• #77 Documentation fix
• #76 Adding XLIB_JASPERREPORTS_IMG to the _remove_user.sql. Fixed the deinstall script.
• #69 Timeout issue when connecting to cloud database. Oracle notification services ons.jar are now removed from the build.

Changed behaviour

• #79 By default, all http requests are now done using XLIB_HTTP.http_version_1_1. If this causes issues in your application, you can downgrade to 1.0. It is a new optional parameter in xlib_jasperreports.show_report and xlib_jasperreports.get_report

Deprecated features (still available but will go away eventually)

• none

Obsoleted features (no longer available)

• none

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
• For running the application on Tomcat10, you have to use jri-2.8.0-jasper-6.18.1-tomcat10.war instead of jri.war.
• #98 reportsPath: default value and relative paths (../reports or ..\reports) don't work

UPDATE: due to bug #98 the current release is removed. Please use https://github.com/daust/JasperReportsIntegration/releases/tag/v2.8.1 instead

Version 2.7.1 (release: 14.12.2021)

You can see the full list of issues with details in the milestones page.

New features

• none

Bug fixes / Security fixes

• #87 - (CVE-2021-44228) Security warning: New zero-day in the Log4j Java library

Changed behaviour

• none

Deprecated features (still available but will go away eventually)

• none

Obsoleted features (no longer available)

• none

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.

Version 2.7.0 (release: 18.11.2020)

You can see the full list of issues with details in the milestones page.

New features

• #66 - Uptake JasperReports Library 6.16.0
• #26 - Connecting to ATP Database
• #63 - Optimization for developers - adding your own .jar files

Bug fixes

• none

Changed behaviour

• none

Deprecated features (still available but will go away eventually)

• none

Obsoleted features (no longer available)

• none

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.

JasperReportsIntegration 2.6.2 (release)

Version 2.6.2 (release: 14.10.2020)

This release contains a number of fixes that came up after the release 2.6.1.

You can see the full list of issues with details in the milestones page.

New features

• #52 - Uptake JasperReports Library 6.15.0

Bug fixes

• #57 - Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
• #53 - Documentation bugs
• #55 - Barcodes produce classnotfounderror
• #54 - Timeout value from default table not working
• #51 - Batch files on Windows throw error: main class not found

Changed behaviour

• none

Deprecated features (still available but will go away eventually)

• none

Obsoleted features (no longer available)

• none

Known issues

• Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues .