Using Developer version 2024.3.3.3946_LTS with the plugin Barcode_Servoy_JasperReports_Plugin_v.2024.3.0_6.21.0 installed, we deployed our application as an NG2 application and get the following error:
ERROR: Exception from plugin: message: <java.lang.Exception: java.lang.SecurityException: class "com.lowagie.text.pdf.FopGlyphProcessor"'s signer information does not match signer information of other classes in the same package>
at _7rCore/scopes/coreReports/generateReport:57 (generateReport)
at HadesReportsKTSH/scopes/rptPersonsNG/viewArchivblattSchueler:577 (viewArchivblattSchueler)
at C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\7r\servoyservices\window\window_server.js:455
Using the same Developer with Barcode_Servoy_JasperReports_Plugin_v.2022.3.1_6.20.0 works without an error message.
are you using the velocity plugin or another 3rd party plugin that uses the itext.jar?
Problem is that Servoy started using the openpdf.jar which is a fork of itext.jar.
I had the same issue (using Velocity) and for that case it was safe to remove the itext.jar from that plugin.
Thanks a lot for your solution! Yes, we use the velocity plugin.
We did remove the iText.jar (in my case iText-4.2.0.jar) in the …/application_server/plugin/velocityreport folder and also have removed the referencing line in the file velocityreport.jar.jnlp.
It works with these changes
I am asking myself if we have to replace iText.jar in the velocityreport folder by the openpdf.jar or can we just delete the iText.jar without any replacemnet? Would that mean velocity report is not needing iText.jar?
huber:
I am asking myself if we have to replace iText.jar in the velocityreport folder by the openpdf.jar or can we just delete the iText.jar without any replacemnet? Would that mean velocity report is not needing iText.jar?
You should not have duplicate jars in your setup.
Also when exporting, Servoy will check for this and will automatically remove the most likely of the duplicates.
In general it is better to keep control over this yourself, so in case you notice duplicate jars, remove them yourself based on the deletes that Servoy does on exporting the war.
huber:
also have removed the referencing line in the file velocityreport.jar.jnlp.
.jnlp files are a smart-client thing, so if you only use (Ti)NG, deleting is fine. In case you are still running smart client you should change the jnlp and point it to the openpdf.jar
As openpdf.jar contains the same classpaths as the prior itext.jar, it’s not that Velocity can ‘do without’, but it will use class paths coming from a different jar.