Teodor Danciu

In JasperReports Library, there are only 3 features that are related/impacted by the so-called Jakarta Migration: - servlets - EJBQL query executer - Hibernate query executer Are you using the JasperReports Library servlets in your own application? Do you have reports having EJB queries or Hibernate queries? If you are not using any of those, than you can use existing JasperReports Library releases for your Tomcat 10 deployment. Please let us know if it does not work. Jakarta support for these 3 features requires extracting them from the core library and offering 2 implementations of them: one for non-Jakarta and the new one for Jakarta. This project of splitting is a work in progress that happens in the release-7.0.0 branch of the library which is published here: https://github.com/TIBCOSoftware/jasperreports/tree/release-7.0.0 Snapshots of the upcoming JRL7 artifacts can be found in our public Maven repository here: https://jaspersoft.jfrog.io/ui/native/jr-ce-snapshots/net/sf/jasperreports/ I hope this helps. Teodor

JRL CE 6.21.2 has been released.

Can you attach your JRXML here?

You should attach your JRXML here so that we could see what could be wrong with it. It is highly unlikely someone would create the JRXML you need from scratch for you.

Can you attach the source JRXML to this post?

Resources are loaded from repository implementations, which can be added to the engine as extensions. So instead of using a custom URL handler, you need to implement a custom repository to load your images from. I hope this helps. Teodor

Fixed at https://github.com/TIBCOSoftware/jasperreports/commit/2cc50475bcc0d777eb18299d266a0596ffc49b84

Indeed, this is a bug we introduced in 6.20.5. Will let you know when fixed.

What is the export format presenting the problem? Is the report viewed in HTML format or PDF format?

Hi, We do not have a precise date for JasperReports 7 release. It is still months away. If you want to use Java 17, you can do that even with JasperReports 6.21.0, and if you need Jakarta servlets, you can copy the ones we have in the library, change the package names inside and use yours. Does not make sense to wait just for that. If you do use other Jakarta related APIs such as our EJBQL query executer or our Hibernate query executer, than that indeed is more complicated and you cannot migrate them on your own easily. I hope this helps. Teodor

I did not suggest to use ISO-8859-1, which is Latin1. I suggested to use Identity-H. I hope this helps. Teodor

Hi, Have you tried to specify <pdfEncoding>Identity-H</pdfEncoding> for your font families? I hope this helps. Teodor