You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Thomas Chojecki (JIRA)" <ji...@apache.org> on 2013/09/17 11:12:02 UTC
[jira] [Resolved] (PDFBOX-1720) BouncyCastle 1.49: ambigous
constructor usage
[ https://issues.apache.org/jira/browse/PDFBOX-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Chojecki resolved PDFBOX-1720.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Assignee: Thomas Chojecki
Gosh. You're right. Skipped the line.
I fixed it in rev 1523961
> BouncyCastle 1.49: ambigous constructor usage
> ---------------------------------------------
>
> Key: PDFBOX-1720
> URL: https://issues.apache.org/jira/browse/PDFBOX-1720
> Project: PDFBox
> Issue Type: Improvement
> Components: PDModel
> Affects Versions: 2.0.0
> Reporter: Tilman Hausherr
> Assignee: Thomas Chojecki
> Priority: Minor
> Fix For: 2.0.0
>
>
> pdfbox\pdmodel\encryption\PublicKeySecurityHandler.java:
> EnvelopedData env = new EnvelopedData(null, derset, encryptedcontentinfo, null);
> is ambigous *if* one would use the latest (1.49) version of bouncycastle and doesn't compile. One has to choose one of the two constructors by setting a type for the last "null". Looking at the constructor for 1.49, the solution would be:
> Solution:
> EnvelopedData env = new EnvelopedData(null, derset, encryptedcontentinfo, (ASN1Set) null);
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira