Feature #1592
Conflicting itext.jar and openpdf.jar (fork of itext) in Servoy 2024.3.x and above
0%
Description
Not really a feature request, but neither a defect or patch:
In v2024.3.0, Servoy ships openpdf.jar which is a fork of itext.jar
When using JasperReports (2024.3 version), the creation of the JasperReport fails due to this error:
class "com.lowagie.text.pdf.FopGlyphProcessor"'s signer information does not match signer information of other classes in the same package
As I'm using velocity for API purposes rather than report creation I've taken out the itext.jar which is fine I guess.
Question though is: how does this effect the velocity plugin when a project wants to benefit from both Velocity and Jasper plugin functionalities.
History
Updated by Patrick Talbot 10 months ago
- Status changed from New to Closed
The conflict here is about the signatures.
If you remove the signatures of all the jars (including the ones in lib/beans/plugins/lafs) then Velocity should be able to work by using the classes that are in the forked openpdf.jar (provided all the classes from iText are present) if you remove the iText jar from you war.
Signed jars are only necessary when using Smart Client.
For Web/NG/Titanium/Velocity where to all the java code is running server side, it's best to have no signatures at all, because this prevent these kinds of conflicts... You can use the CodeSigner tool to do that.