Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0
-
Fix Version/s: 4.0
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:Java 1.5, 1.6
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
When I was working on PDF-130, I was running the tagging on the calgary transit 2004 PDF, using Java 1.5, and it worked just fine. When I switched to using Java 1.6, I got an exception related to loading Bouncy Castle.
This might be due to changes to the reflection code that I made forPDF-127, where I changed the SecurityManager reflection code to not happen in the constructor, but instead happen statically. That change should be investigated.
Also, I noticed that Java 1.6 includes a Sun JCE provider, whereas Java 1.5 does not. This could indicate a conflict between BouncyCastle and the Sun JCE provider. Possibly a newer version of BouncyCastle may address any conflict.
We should see if BouncyCastle is even necessary with Java 1.6. Potentially we may need it for its RC4 implementation.
This might be due to changes to the reflection code that I made for
Also, I noticed that Java 1.6 includes a Sun JCE provider, whereas Java 1.5 does not. This could indicate a conflict between BouncyCastle and the Sun JCE provider. Possibly a newer version of BouncyCastle may address any conflict.
We should see if BouncyCastle is even necessary with Java 1.6. Potentially we may need it for its RC4 implementation.
Actually, Sun's 1.5 JVM and up include a JCE provider, and it even has RC4 support. So BouncyCastle might not be necessary anymore.
http://java.sun.com/j2se/1.5.0/docs/guide/security/jce/JCERefGuide.html#SupportRSAEncryption
I'll need to check-out the Mac JVM and see about its JCE provider.