You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Removal of the PDF tagging code in 7.0.8 is a breaking change in a patch release #601
After updating from 7.0.7 to 7.0.8, we were surprised to encounter the following error:
net.sf.jasperreports.engine.JRRuntimeException: Tagged PDF export is not supported. See https://jasperreports.sourceforge.net/config.reference.html#net.sf.jasperreports.export.pdf.tagger.factory
To avoid the error and thus ignore the tagged PDF export settings, you should set this property to net.sf.jasperreports.pdf.common.SilentPdfTaggerFactory, which produces documents without tags.
For proper tagged PDF output, please consider upgrading to JasperReports Library Professional, from Jaspersoft.
Just to confirm, there's no longer any way to make PDF/A documents using the Community Edition?
No comment on hollowing out the Community Edition, but one wouldn't expect breaking changes like this in a patch release.
@dadza yes it looks like you added methods that don't exist in 1.3.43 for example in your ClassicPdfStructureTreeRoot it looks like you added a setStructureTreeRoot that does not exist.
com.lowagie.text.pdf.PdfWriter.setStructureTreeRoot(com.lowagie.text.pdf.PdfStructureTreeRoot).
This error is reported at image build time because class net.sf.jasperreports.pdf.classic.ClassicPdfStructureTreeRoot
JasperReports checks at runtime whether it's running with the custom OpenPDF or with the stock one, and it only calls the setStructureTreeRoot in the first case. See
if (ClassicPdfUtils.isCustomStructureTreeRootSupported())
The ClassicPdfStructureTreeRoot class, which calls the setStructureTreeRoot method, is only used when the custom OpenPDF jar is detected.
The problem in your case is that the graalvm native compiler attempts to link the ClassicPdfStructureTreeRoot class and fails when using the stock OpenPDF jar as it doesn't find the setStructureTreeRoot method. I'm not familiar with the graalvm native compiler, if there's an option to exclude the ClassicPdfStructureTreeRoot class then the problem would be solved.
We are planning to submit pull requests to the OpenPDF project, but for the moment we must rely on the custom jar.
This is a really unfortunate change. Removing PDF tagging/PDF/A support from the Community Edition is one thing — but doing it in a 7.0.7 to 7.0.8 patch release is quite another.
A patch release should not silently remove existing functionality and turn a previously working configuration into a runtime exception.
We will now have to pin JasperReports to 7.0.7 indefinitely unless we move to the Professional Edition or replace the PDF functionality entirely.
That's a rather creative interpretation of semantic versioning.
I agreed, but unfortunately, it is something that cannot be fixed, so we would have to live with it.
Keeping talking about it is not going to solve it.
We'll pay more attention in the future, but this one is behind us now.
For some background context for anyone following this: Jaspersoft was recently acquired by HCLSoftware and I suspect there's corporate pressure involved in this decision. I expect this is only the beginning and that we'll see more features getting removed from the open source version soon.
For Teodor: A passive-aggressive response like that is not a great way to get people into upgrading to the paid version..
@uweguenther, what we ended up doing as a quick fix while looking into other options, was to generate the PDF with Jasper into a temp file and then convert it to PDF/A manually. We were lucky to already have a PDF/A converter service running in our env but regardless, it shouldn't require too much code to do it with OpenPDF or PDFBox, for example.
When I said this cannot be fixed, I mainly wanted to say that we cannot pull back 7.0.8 from public Maven repositories and re-release it.
I also wanted to convey that, most likely, there will be no 7.0.9 release to fix this, which came in as passive aggressive.
But my main intention was to set the right expectations.
This step back is highly unlikely because of the very nature of the situation: a minor release introduced rather big changes. It's not only about the error message raised, but also about a new artifact being introduced, while the feature was removed.
Going forward, projects that need the tagged PDF functionality from the JasperReports Library Community Edition will have to pin down version 7.0.7, as there will be no 7.0.9 that temporarily brings the feature back.
I hope users understand that open source projects such as the JasperReports Library, backed by commercial enterprises, are always trying to find the right balance between what is available for free and what they can sell to keep the projects going.
There is competition in the open source space too and you have to adjust to what your competitors are doing.
Jaspersoft is doing this for more than 20 years now and I hope it did not disappoint too many during all this time.
Activity
teodord commentedon Aug 11, 2026
I confirm that producing PDF/A documents is no longer possible with Community Edition alone.
I also agree that maybe a second digit increase would have been more appropriate for this release, and was probably an oversight.
Thank you,
Teodor
melloware commentedon Aug 13, 2026
also its still using custom
1.3.43.jaspersoft.2even though the release notes say it works with standard 1.3.43 i can confirm it does not.melloware commentedon Aug 13, 2026
Our Quarkus JasperREports native build fails because of this: quarkiverse/quarkus-jasperreports#290
dadza commentedon Aug 14, 2026
Can you detail the problem you have with JasperReports 7.0.8 and OpenPDF 1.3.43?
Thank you,
Lucian
melloware commentedon Aug 14, 2026
@dadza yes it looks like you added methods that don't exist in 1.3.43 for example in your
ClassicPdfStructureTreeRootit looks like you added asetStructureTreeRootthat does not exist.See our build failing: https://github.com/quarkiverse/quarkus-jasperreports/actions/runs/31396110164/job/93479311451
melloware commentedon Aug 14, 2026
@dadza if you guys are making fixes to OpenPDF you really should be getting these changes merged back upstream.
dadza commentedon Aug 14, 2026
JasperReports checks at runtime whether it's running with the custom OpenPDF or with the stock one, and it only calls the setStructureTreeRoot in the first case. See
jasperreports/ext/pdf/src/main/java/net/sf/jasperreports/pdf/classic/ClassicPdfStructure.java
Line 61 in 2da2e11
The ClassicPdfStructureTreeRoot class, which calls the setStructureTreeRoot method, is only used when the custom OpenPDF jar is detected.
The problem in your case is that the graalvm native compiler attempts to link the ClassicPdfStructureTreeRoot class and fails when using the stock OpenPDF jar as it doesn't find the setStructureTreeRoot method. I'm not familiar with the graalvm native compiler, if there's an option to exclude the ClassicPdfStructureTreeRoot class then the problem would be solved.
We are planning to submit pull requests to the OpenPDF project, but for the moment we must rely on the custom jar.
Regards,
Lucian
melloware commentedon Aug 14, 2026
ok let me try and exclude it and see
melloware commentedon Aug 15, 2026
@dadza i got it working with this PR. Had to GraalVM remove the ClassicPdfStructureTreeRoot.
https://github.com/quarkiverse/quarkus-jasperreports/pull/290/changes
dadza commentedon Aug 20, 2026
FYI two OpenPDF pull requests have been created for the Jaspersoft OpenPDF 1.3.43 changes:
LibrePDF/OpenPDF#1617
LibrePDF/OpenPDF#1618
Regards,
Lucian
uweguenther commentedon Aug 21, 2026
This is a really unfortunate change. Removing PDF tagging/PDF/A support from the Community Edition is one thing — but doing it in a 7.0.7 to 7.0.8 patch release is quite another.
A patch release should not silently remove existing functionality and turn a previously working configuration into a runtime exception.
We will now have to pin JasperReports to 7.0.7 indefinitely unless we move to the Professional Edition or replace the PDF functionality entirely.
That's a rather creative interpretation of semantic versioning.
teodord commentedon Aug 21, 2026
I agreed, but unfortunately, it is something that cannot be fixed, so we would have to live with it.
Keeping talking about it is not going to solve it.
We'll pay more attention in the future, but this one is behind us now.
Thank you,
Teodor
ojaha065 commentedon Aug 23, 2026
Well, the semantically correct way of fixing this would be to make another point release with the breaking change reverted. If you wanna follow semantic versioning, API incompatible changes like this require a new major version.
For some background context for anyone following this: Jaspersoft was recently acquired by HCLSoftware and I suspect there's corporate pressure involved in this decision. I expect this is only the beginning and that we'll see more features getting removed from the open source version soon.
For Teodor: A passive-aggressive response like that is not a great way to get people into upgrading to the paid version..
@uweguenther, what we ended up doing as a quick fix while looking into other options, was to generate the PDF with Jasper into a temp file and then convert it to PDF/A manually. We were lucky to already have a PDF/A converter service running in our env but regardless, it shouldn't require too much code to do it with OpenPDF or PDFBox, for example.
teodord commentedon Aug 24, 2026
When I said this cannot be fixed, I mainly wanted to say that we cannot pull back 7.0.8 from public Maven repositories and re-release it.
I also wanted to convey that, most likely, there will be no 7.0.9 release to fix this, which came in as passive aggressive.
But my main intention was to set the right expectations.
This step back is highly unlikely because of the very nature of the situation: a minor release introduced rather big changes. It's not only about the error message raised, but also about a new artifact being introduced, while the feature was removed.
Going forward, projects that need the tagged PDF functionality from the JasperReports Library Community Edition will have to pin down version 7.0.7, as there will be no 7.0.9 that temporarily brings the feature back.
I hope users understand that open source projects such as the JasperReports Library, backed by commercial enterprises, are always trying to find the right balance between what is available for free and what they can sell to keep the projects going.
There is competition in the open source space too and you have to adjust to what your competitors are doing.
Jaspersoft is doing this for more than 20 years now and I hope it did not disappoint too many during all this time.
Thank you,
Teodor
dldnhf commentedon Oct 1, 2026
Will you release a 7.0.7.1 in case of a vulnerability?