在Eclipse的kepler中运行OSGI工程出错的解决方案
来源:互联网 发布:岁月神偷 网络歌手 编辑:程序博客网 时间:2024/06/06 06:32
今天学习OSGI的过程中按照书上所述搭建好第一个helloworld插件工程,运行的过程中出现下面所示的错误:
!SESSION 2014-06-09 21:04:49.038 -----------------------------------------------eclipse.buildId=unknownjava.version=1.6.0_35java.vendor=Sun Microsystems Inc.BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_USCommand-line arguments: -dev file:E:/XJTU/.metadata/.plugins/org.eclipse.pde.core/Hello OSGI/dev.properties -os win32 -ws win32 -arch x86_64 -consoleLog -console!ENTRY org.eclipse.osgi 4 0 2014-06-09 21:04:49.616!MESSAGE Could not find bundle: org.eclipse.equinox.console!STACK 0org.osgi.framework.BundleException: Could not find bundle: org.eclipse.equinox.console at org.eclipse.osgi.framework.internal.core.ConsoleManager.checkForConsoleBundle(ConsoleManager.java:211) at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:298) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426)于是乎上网google发现需要同时引入org.eclipse.equinox.console这个bundle,赶紧照做,如下图所示
原以为就此可以大功告成,不料...,看下文(等待我的是更多的Exception)
!SESSION 2014-06-09 21:09:17.097 -----------------------------------------------eclipse.buildId=unknownjava.version=1.6.0_35java.vendor=Sun Microsystems Inc.BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_USCommand-line arguments: -dev file:E:/XJTU/.metadata/.plugins/org.eclipse.pde.core/Hello OSGI/dev.properties -os win32 -ws win32 -arch x86_64 -consoleLog -console!ENTRY org.eclipse.equinox.console 4 0 2014-06-09 21:09:17.725!MESSAGE FrameworkEvent ERROR!STACK 0org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.console_1.0.100.v20130429-0953 [6]" could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.felix.service.command; version="0.8.0" at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)!ENTRY org.eclipse.osgi 4 0 2014-06-09 21:09:17.725!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.console_1.0.100.v20130429-0953.jar was not resolved.!ENTRY org.eclipse.osgi 4 0 2014-06-09 21:09:17.725!MESSAGE Could not start bundle: org.eclipse.equinox.console!STACK 0org.osgi.framework.BundleException: Could not start bundle: org.eclipse.equinox.console at org.eclipse.osgi.framework.internal.core.ConsoleManager.checkForConsoleBundle(ConsoleManager.java:217) at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:298) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426)Caused by: org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.console_1.0.100.v20130429-0953 [6]" could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.felix.service.command; version="0.8.0" at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300) at org.eclipse.osgi.framework.internal.core.ConsoleManager.checkForConsoleBundle(ConsoleManager.java:215) ... 10 moreRoot exception:org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.console_1.0.100.v20130429-0953 [6]" could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.felix.service.command; version="0.8.0" at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300) at org.eclipse.osgi.framework.internal.core.ConsoleManager.checkForConsoleBundle(ConsoleManager.java:215) at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:298) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426)!ENTRY org.eclipse.osgi 2 0 2014-06-09 21:09:17.735!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:!SUBENTRY 1 org.eclipse.osgi 2 0 2014-06-09 21:09:17.735!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.console_1.0.100.v20130429-0953.jar was not resolved.!SUBENTRY 2 org.eclipse.equinox.console 2 0 2014-06-09 21:09:17.735!MESSAGE Missing imported package org.apache.felix.service.command_0.8.0.!ENTRY org.eclipse.osgi 2 0 2014-06-09 21:09:17.745!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:!SUBENTRY 1 org.eclipse.osgi 2 0 2014-06-09 21:09:17.745!MESSAGE Bundle org.eclipse.equinox.console_1.0.100.v20130429-0953 [6] was not resolved.!SUBENTRY 2 org.eclipse.equinox.console 2 0 2014-06-09 21:09:17.745!MESSAGE Missing imported package org.apache.felix.service.command_0.8.0.!SUBENTRY 2 org.eclipse.equinox.console 2 0 2014-06-09 21:09:17.745!MESSAGE Missing optionally imported package org.osgi.service.cm_0.0.0.实在是郁闷的慌,于是乎又开始各种search...
终于找到了终极解决方案,即再次加入三个org.eclipse.equinox.console必须的依赖bundle,分别是:
org.apache.felix.gogo.command
org.apache.felix.gogo.runtime
org.apache.felix.gogo.shell
概括一下:当Run时报错,只选种org.eclipse.equinox.console时还是会报错,那时因为OSGI组建之间存在依赖关系,要使用 org.eclipse.equinox.console必须要有它需要依赖的OSGI组建,因此在调试时,除了选择自己编写的OSGI组建还要选择上面的三个bundle。貌似这个问题在之前的Eclipse版本中没有滴,估计是进一步的重构之后的缘故。总之,按照这种方式就可以顺利的Run了。在osgi>提示符输入ss命令,可以看到如下的详情:
可以看到HelloWorld bundle已经被安装并且解析完成,但是还没有启动(这是因为我设置的是不自动start);
在osgi>提示符后面输入start 1,然后再次ss,会发现helloworld bundle已经启动(ACTIVE)。
0 0
- 在Eclipse的kepler中运行OSGI工程出错的解决方案
- eclipse运行出错的解决方案
- 在Eclipse中新建Android工程后出错的问题
- OSGi的Helloworld!(Eclipse-kepler-SR2及对应的Equinox)
- 在Eclipse中运行工程出现.apk找不到的错
- 在eclipse中运行使用maven构建的web工程
- 使用eclipse创建在myeclipse中运行的web工程
- 在eclipse中导入的工程无法正常运行
- MAVEN在eclipse(kepler)里的安装配置
- 在Eclipse Kepler中支持Java 8
- 设置eclipse kepler 中tomcat的启动参数
- 如何在eclipse中基于maven创建osgi的bundle
- SQL SERVER 2005 在Windows7 中运行出错 error:26 的解决方案
- 在eclipse中利用spring-osgi中的测试框架对osgi 的 boundle进行测试
- Eclipse工程中Android Dependencies出错的解决方式
- 关于在eclipse中运行出错的一个小问题 Unknown column 'android' in 'where clause'
- 解决方案-在Mac系统中,Eclipse无法导入含有中文路径的工程
- 在Eclipse中调试运行launcher源码(三)——修改工程的包名
- Longest Common Prefix
- jQuery setTimeout传递字符串参数报错怎么办?解决方法
- 将ibatis的sql打印在控制台
- 【leetcode】Climbing Stairs
- 【LeetCode】Longest Valid Parentheses
- 在Eclipse的kepler中运行OSGI工程出错的解决方案
- An Introduction To Tkinter
- POJ 3370 Halloween treats 鸽巢原理 解题
- 回文数的判断
- Unity3D调用第三方SDK(之一)从eclipse到Unity3D.
- Android xml配置动画效果
- HPUX---hpux的核心参数
- 数据挖掘技术、方法及应用
- MyEclipse10整合Git,并在Github上发布项目