Do you know if the com.sun.crypto.provider package is actually available on
the boot class path? If it is available on the extension class loader from
the VM then that may be the cause since Equinox only uses the boot class
loader by default.
I am trying to integrate some pre-existing code that relies on the
com.sun.crypto.provider.SunJCE class into our Equinox based
application (version 3.7.1). Now I know by default the com.sun
packages are not accessible to bundles, so I made a fragment with the
idea of extending the framework to export the package. Here is its
Clue 2: The PDE marks the instantiation with an access restriction.
Despite the two errors, the project does compile and I am able to
start debugging. When starting the sample bundle, I receive a class
not found exception (see attached txt file for the complete stack
trace). However, when I do a "packages 0" in the console, it appears
Equinox is claiming to export this package: