Try setting the following configuration property:
osgi.frameworkParentClassloader=ext
In PDE you can try this by setting the VM argument (e.g.
-Dosgi.frameworkParentClassloader=ext). The org.eclipse.equinox.launcher
(used both from PDE and the eclipse native launcher to launch the equinox
framew
Tom,
Listing out the system properties gives me sun.boot.class.path which I
think is what you are after, right? If so, the sunjce_provider.jar is
not present. It appears the boot path is only getting jars at the
jre/lib directory and not any sub directories (e.g.
jre/lib/ext/sunjce_provider.jar).
> Clue 1: The PDE marks the Export-Package line and says that
> com.sun.crypto.provider does not exist in this plugin.
This has been a long-standing problem in PDE, but nobody appears to have filed
a bug. So I recently filed
"Package does not exist in this plug-in" errors with extensio
Tom,
Thank you for the reply. I'm still kind of new to Equinox. What is a
good way to tell if it is on the boot class path?
Ben
On Thu, Feb 23, 2012 at 9:59 AM, Thomas Watson wrote:
> s availab
___
equinox-dev mailing list
equinox-dev@eclipse.org
http
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.
Tom
|>
| From: |
|>
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 expo
