search

makdimka077 / xades4j

Automatically exported from code.google.com/p/xades4j
GNU Lesser General Public License v3.0
0 stars 0 forks source link

Remove direct reference to sun.security.pkcs11.SunPKCS11 #31

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Try to compile the project on a platform that doesn't have 
sun.security.pkcs11.SunPKCS11

What version of the product are you using? On what operating system?
1.2.0, Windows 64 (SunPKCS11 is not available on that platform)

Please provide any additional information below :

The attached patch is a possible solution using reflection. 
However I have actually not fully tested it.

Original issue reported on code.google.com by jmdesp on 8 Dec 2011 at 12:49

Attachments:

GoogleCodeExporter commented 9 years ago 
This allows for compilation using 64-bit Windows JDK, but it doesn't fix the 
problem -- PKCS #11 is unavailable on this platform. You need to use 32bit JRE 
and JDK for PKCS#11 to work on Windows. As per documentation[1], 64bit Solaris 
or 64bit Linux don't have such limitation.

I don't know if (or when) Oracle intends to fix that. But it looks like OpenJDK 
people are working on it[2].

  [1]: http://docs.oracle.com/javase/6/docs/technotes/guides/security/p11guide.html#Requirements
  [2]: http://openjdk.java.net/jeps/131

Original comment by hubert.k...@gmail.com on 21 Sep 2012 at 11:35

GoogleCodeExporter commented 9 years ago 
PKCS #11 is unavailable under 64-bit Windows JDK, and I don't expect xades4j to 
fix that problem.

I'd like xades4j to fix the problem that the xades4j package as delivered won't 
compile under 64-bit Windows JDK, which also hits all the people who don't 
intend to use PKCS#11. And probably it won't compile either under many 
non-Oracle JVM implementation because sun.security.pkcs11.SunPKCS11 is not part 
of the standardized Java SDK API.
You can mark this issue fixed as soon as that part of the problem is solved.

Original comment by jmdesp on 7 Oct 2012 at 8:31

GoogleCodeExporter commented 9 years ago 
I'm considering reorganizing provider implementations and moving them into 
separate jars.

Original comment by luis.fgoncalv on 7 Oct 2012 at 6:52

GoogleCodeExporter commented 9 years ago 
The provider is now loaded using reflection (r253).

Original comment by luis.fgoncalv on 27 Jan 2014 at 10:44