在保险丝/ Karaf接线包例外 [英] Wiring package exceptions in Fuse/Karaf

查看:303
本文介绍了在保险丝/ Karaf接线包例外的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在许多项目中,我碰到这个例外来了。有什么能为这个异常的原因?

In many projects, I have came across this exception. What could be the reason for this exception ?

据我了解,这可能是因为版本不一致的使用。可能是什么其他可能的方案是什么?

According to my knowledge, it can be because of inconsistent version usage. What could be the other possible scenarios ?

这是因为骆驼版本,我们在项目中使用?请帮助。

Is this because of the Camel version we are using in the project ?Please help.

org.osgi.framework.BundleException:捆绑未解决约束com.test.div.soa.module-通知[324]:无法解析324.0:缺少需求[324.0] osgi.wiring.package; (安培;!(osgi.wiring.package = org.apache.camel)(版本> = 2.11.0)((版本> = 3.0.0)))
                在org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4155)[org.apache.felix.framework-4.0.3.redhat-60024.jar:]
                在org.apache.felix.framework.Felix.startBundle(Felix.java:2055)[org.apache.felix.framework-4.0.3.redhat-60024.jar:]
                在org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-60024.jar:]
                在org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1247)[7:org.apache.felix.fileinstall:3.3.11.redhat-60024]
                在org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1219)[7:org.apache.felix.fileinstall:3.3.11.redhat-60024]
                在org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:508)[7:org.apache.felix.fileinstall:3.3.11.redhat-60024]
                在org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:291)[7:org.apache.felix.fileinstall:3.3.11.redhat-60024]

org.osgi.framework.BundleException: Unresolved constraint in bundle com.test.div.soa.module-notify[324]: Unable to resolve 324.0: missing requirement [324.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.camel)(version>=2.11.0)(!(version>=3.0.0))) at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4155)[org.apache.felix.framework-4.0.3.redhat-60024.jar:] at org.apache.felix.framework.Felix.startBundle(Felix.java:2055)[org.apache.felix.framework-4.0.3.redhat-60024.jar:] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-60024.jar:] at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1247)[7:org.apache.felix.fileinstall:3.3.11.redhat-60024] at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1219)[7:org.apache.felix.fileinstall:3.3.11.redhat-60024] at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:508)[7:org.apache.felix.fileinstall:3.3.11.redhat-60024] at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:291)[7:org.apache.felix.fileinstall:3.3.11.redhat-60024]

问候
大师

推荐答案

您包,我以为是将其复制到ESB的部署目录,而不是使用使用OSGi的更合适的方式安装:安装命令

Your bundle, which I assume is installed by copying it to the deploy directory of the ESB instead of using the more appropriate way of using osgi:install command.

反正你的包需要骆驼2.11,而ESB来开箱与骆驼2.10。因此,改变你的包使用骆驼2.10附带的ESB。

Anyway your bundle requires Camel 2.11, and the ESB comes out of the box with Camel 2.10. So change your bundle to use Camel 2.10 which is shipped with the ESB.

这篇关于在保险丝/ Karaf接线包例外的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆