On 4/20/10 15:36, Shrivallabh Deshmukh wrote:
Once I did that, it started cribbing for sun internal packages. Isnt there a
simpler method to ensure that all jdk classes are available by default?
Not really. Bundles have to express their dependencies.
However, javax.* packages shouldn't have any issue finding sun internal
packages, unless you are saying your bundle is using these sun internal
packages, in which case you need to import them too (and export them
from the system bundle using org.osgi.framework.system.packages.extra
property).
-> richard
On Wed, Apr 21, 2010 at 12:34 AM, Ali Naddaf<[email protected]> wrote:
I believe you need to import javax.* packages explicitly; only java.*
packages are visible by default.
Ali.
On 4/20/2010 1:59 PM, Shrivallabh Deshmukh wrote:
My plugin uses the webservices api which relies on creating an https
connection.
The bundle class loader cannot resolve the classes present with the jre
(jsse jar)
java.lang.NoClassDefFoundError: javax/net/ssl/HostnameVerifier
I tried adding jsse.jar explicitly using the manifest (duplicate classes
loaded by the classloader), then it began to crib about internal sun
packages.
Any idea why this could be happening? Is there any reason why the bundle
class loader would not see these classes?
Regards
Shrivallabh
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
