Eclipse Community Forums: Virgo » com.sun.crypto.provider Import-Package could not be resolved.

Help

Home

Home » Eclipse Projects » Virgo » com.sun.crypto.provider Import-Package could not be resolved.

Show: Today's Messages :: Show Polls :: Message Navigator

com.sun.crypto.provider Import-Package could not be resolved. [message #539470]

Thu, 10 June 2010 21:08

No real name

Messages: 2
Registered: June 2010

Junior Member

How do you configure spring-dm to resolve the unresolved dependencies? I thought for the system packages these are just passed through to the classloader to resolve?

Caused by: com.springsource.kernel.osgi.framework.UnableToSatisfyBundle DependenciesException: Unable to satisfy dependencies of bundle 'com.bundle' at version '1.0.1': Cannot resolve: com.bundle
Resolver report:
An Import-Package could not be resolved. Caused by missing constraint in bundle <com.bundle_1.0.1>
constraint: <Import-Package: com.sun.crypto.provider; version="1.6.0">

at com.springsource.kernel.install.pipeline.stage.resolve.inter nal.QuasiResolveStage.process(QuasiResolveStage.java:54)

Report message to a moderator

Re: com.sun.crypto.provider Import-Package could not be resolved. [message #539515 is a reply to message #539470]

Fri, 11 June 2010 07:35

Glyn Normington

Messages: 1222
Registered: July 2009

Senior Member

The answer is the same for Virgo. The java6-server.profile in the lib directory has a boot delegation property (org.osgi.framework.bootdelegation). Packages listed in that property will be obtained by delegation to the boot class loader (actually the class loader that loaded the OSGi framework). Wildcards are allowed in this property, so org.foo.* includes org.foo.x, org.foo.x.y, etc. (but not org.foo which would need to be specified separately).

However, the default version of java6-server.profile includes com.sun.* in the boot delegation property. So you don't need to import these packages in your bundles and I would recommend not importing them because this will tie your manifests to particular JRE implementations (those based on Sun's).

Alternatively, if you really must import these packages for some reason, you can add the relevant packages to the system packages property (org.osgi.framework.system.packages). In this case you should specify each package individually and, if version 0 is not appropriate, specify what version you want the package to be exported with.

Take a look at the profile and I'm sure this will help.

Report message to a moderator

Previous Topic:	Virgo (Spring DM Server) Clustering
Next Topic:	com.sun.crypto.provider Import-Package could not be resolved.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 13:42:06 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter