PdfSignature Plugin

[Roberto Blasco]

Hi all.

I'm rewriting the PdfSignature plugin with the new version of iText (5.3.4). This version has the AFFERO GENERAL PUBLIC LICENSE (AGPL).

Is it ilegal to place this plugin in Servoy Forge with this kind of license?

Best regards. Roberto Blasco

[ROCLASI]

Hi Roberto,

AGPL complies with the Open Source Definition and is also reviewed and approved by The Open Source Initiative (OSI).
So to answer your question, a component with the AGPL license is fine to be hosted on ServoyForge.

[Roberto Blasco]

Thanks a lot ROCLASI.

[ptalbot]

Roberto, just be aware that most other plugins (Jasper/Velocity/PDF output) are still using v3.1.7 of iText, so using a newer version in your plugin will introduce some compatibility issues with these other plugins...

[Roberto Blasco]

Thanks ptalbot

The libraries are placed in a separate directory inside the plugins directory

[+] plugins
- jpdfsign.jar
- jpdfsign.jar.jnlp
[+] jpdfsing
- bcpkix-jdk15on-1.47.jar
- bcprov-jdk15on-1.47.jar
-itextpdf-5.3.4.jar

There will be compatibility issues with this structure?

Best Regards. Roberto Blasco,

[ptalbot]

Doesn't matter where iText is placed, all the jars in /plugins will be loaded (in headless and web client and in developer and via their respective jnlp for smart client). If another version is somewhere in your plugins directory, then there's no guarantee which version will be loaded first and used (could be 3.1.7 or your 5.3.4), so you will probably have some ClassNotFoundException or MethodNotFoundException at some point, either in your PDFSignature plugin or in Jasper/Velocity/PDF output plugins. There's only one classloader in the end.

[Roberto Blasco]

Ok, thanks, ptalbot.