Ask Your Question
0

could not be resolved. Reason: Missing Constraint: Import-Package: javax.jms;

asked 2016-05-02 06:16:36 -0700

dpkakollu gravatar image

Hi,

I had deployed (copied jar into deploy folder) one of my JMS plugin jar (which is working on opendaylight hydrogen) to distribution-karaf-0.4.0-Beryllium,when I start karaf I am getting an error:

org.osgi.framework.BundleException: The bundle "org.sdnmq.jms_0.1.0.SNAPSHOT [64]" could not be resolved. Reason: Missing Constraint: Import-Package: javax.jms; version="[1.1.0,2.0.0)"

at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)[org.eclipse.osgi-3.8.2.v20130124-134944.jar:]
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)[org.eclipse.osgi-3.8.2.v20130124-134944.jar:]
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)[org.eclipse.osgi-3.8.2.v20130124-134944.jar:]
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)[org.eclipse.osgi-3.8.2.v20130124-134944.jar:]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1245)[7:org.apache.felix.fileinstall:3.4.2]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1217)[7:org.apache.felix.fileinstall:3.4.2]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:509)[7:org.apache.felix.fileinstall:3.4.2]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[7:org.apache.felix.fileinstall:3.4.2]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[7:org.apache.felix.fileinstall:3.4.2]

even all required jar available in system folder I am getting this error. any help.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-05-16 05:29:28 -0700

jgoodyear gravatar image

Having the jar in the system folder doesn't install said jar into the class path. The system folder is just a flat file Maven Repository.

You'll need to using Bundle install command to put that jar into your running container's class path.

If the JMS jar is not an OSGi bundle, than you'll want to use bundle:install wrap:mvn:bundleCoordinates

edit flag offensive delete publish link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

Follow
1 follower

Stats

Asked: 2016-05-02 06:16:36 -0700

Seen: 723 times

Last updated: May 16 '16