Paulo, Maybe there is a better way.
I have 2 motivating factors: 1. Limit the deployment size. The bouncy castle jars are as large as the iText jar. Maybe a 'thin" BC can be distributed with iText that only contains the ASN functions? Or just implement the ASN1 functions in iText? 2. Limit the outside dependencies. Since iText uses the BC api directly, there might be compatibility problems in the future if the BC api changes, yet other systems need the latest BC api. I am trying to avoid Windows 'DLL Hell'. If the JCE does not cover needed "complex" operations that are required, then I can see the need for using BC directly. But it seems that most of these are fairly simple utility methods (if I understand it correctly). Maybe if you were more specific about what is needed in BC that is not available in JCE, I can work on writing that code. Robert ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://itext.ugent.be/itext-in-action/
