问题描述
在很多项目中，我都遇到过这个异常.此异常的原因可能是什么?
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 ?
这是因为我们在项目中使用的 Camel 版本吗?请帮忙.
Is this because of the Camel version we are using in the project ?Please help.
org.osgi.framework.BundleException: 捆绑包 com.test.div.soa.module-notify[324] 中未解决的约束:无法解决 324.0:缺少需求 [324.0] osgi.wiring.package；(&(osgi.wiring.package=org.apache.camel)(version>=2.11.0)(!(version>=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:install 命令来安装的.
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.
无论如何，您的包需要 Camel 2.11，而 ESB 随 Camel 2.10 开箱即用.因此，请更改您的包以使用随 ESB 一起提供的 Camel 2.10.
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.
这篇关于Fuse/Karaf 中的接线包异常的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！