简体   繁体   English

无法解决导入包部署Flex UI项目中的错误

[英]An Import-Package could not be resolved Error in Deploying Flex UI project

I am developing simple VSphere Web Client plugin in Eclipse Juno with Vijava 5.5 and Vsphere sdk 5.5.. My project was working fine till yesterday. 我正在使用Vijava 5.5和Vsphere sdk 5.5在Eclipse Juno中开发简单的VSphere Web Client插件。 Today I tried to change the sdk to Vsphere sdk 6.0. 今天,我尝试将sdk更改为Vsphere sdk 6.0。 From that onwards I am getting Following Error while deploying my UI project in Virgo Server. 从那时起,我在Virgo Server中部署UI项目时遇到“跟随错误”。

Later, I again reverted to my Vsphere sdk 5.5 itself. 后来,我再次恢复了我的Vsphere SDK 5.5本身。 But still i am getting this error. 但我仍然收到此错误。 I don't know what I missed. 我不知道我错过了什么。 Why it showing in my UI project? 为什么它显示在我的UI项目中? Is there anything i can change my dependencies there? 有什么我可以更改我的依赖关系的地方吗?

Error is, 错误是

2015-06-11 19:27:26.160] [INFO ] TCP Connection(11)-127.0.0.1  <DE0004I> Starting bundle 'test-provider' version '0.0.0'.

[2015-06-11 19:27:26.160] [INFO ] start-signalling-1            <DE0005I> Started bundle 'test-provider' version '0.0.0'. 

[2015-06-11 19:27:26.957] [INFO ] TCP Connection(11)-127.0.0.1  <DE0000I> Installing bundle 'com.mycompany.testui.testui' version '1.0.0'. 

[2015-06-11 19:27:27.051] [INFO ] TCP Connection(11)-127.0.0.1  <ME0003I> Dump 'C:\ProgramData\vmware\vSphere Web Client\serviceability\dump\2015-06-11-19-27-051' generated 

[2015-06-11 19:27:27.066] [ERROR] TCP Connection(11)-127.0.0.1  <DE0002E> Installation of bundle 'com.mycompany.testui.testui' version '1.0.0' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.mycompany.testui.testui' at version '1.0.0': Cannot resolve: com.mycompany.testui.testui
    Resolver report:
        An Import-Package could not be resolved. Resolver error data <Import-Package: com.mycompany.testprovider; version="0.0.0">. Caused by missing constraint in bundle <com.mycompany.testui.testui_1.0.0>
             constraint: <Import-Package: com.mycompany.testprovider; version="0.0.0">

    at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:46)
    at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
    at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:73)
    at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
    at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
    at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
    at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:359)
    at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:185)
    at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:140)
    at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:253)
    at org.eclipse.virgo.kernel.deployer.management.StandardDeployer.deploy(StandardDeployer.java:52)
    at sun.reflect.GeneratedMethodAccessor99.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:75)
    at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:279)

部署UI时,必须事先部署服务com.mycompany.test

Service provider is not linked with Plugin UI project. 服务提供者未与插件UI项目链接。 In order to do that, need to do the following.. 为此,需要执行以下操作。

Right-click on the Plugin UI project and select vSphere SDK Tools > Package vSphere Client plugin. 右键单击Plugin UI项目,然后选择vSphere SDK Tools>打包vSphere Client插件。

In that, select your service provider project. 在那,选择您的服务提供商项目。 That's it. 而已。

To make sure the service bundle is deployed before the ui bundle use the <bundlesOrder> tag in the plugin-package.xml . 为了确保在ui捆绑包之前部署了服务捆绑包,请使用plugin-package.xml<bundlesOrder>标记。

vSphere Client (HTML) versions 6.5U1 and above improve on this by introducing a dedicated scope for each plugin (OSGi sandboxing feature). vSphere Client(HTML)6.5U1及更高版本对此进行了改进,为每个插件引入了专用范围(OSGi沙盒功能)。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 捆绑XYZ无法解决。 原因:缺少约束:导入包:ABC; 无头RCP独立版本中的版本=“1.0.0”错误 - The bundle XYZ could not resolved. Reason: Missing Constraint: Import-Package: ABC; version=“1.0.0” error in headless RCP standalone 如何解决要求:导入包: - How to resolve requirement: Import-Package: 为什么此OSGi导入包不起作用? - Why does this OSGi Import-Package not work? Eclipse Oxygen插件缺少约束:Import-Package - Eclipse Oxygen plug-in Missing Constraint: Import-Package 以编程方式验证 OSGi 捆绑依赖项(导入包) - Verify OSGi bundles dependencies (import-package) programmatically 创建Eclipse Maven项目时无法解决工件错误 - artifacts could not be resolved error while creating Eclipse Maven project 类型无法解决错误 - Type Could Not Be Resolved Error 未解决的要求:在Kura Emulator中启动捆绑包时,导入包:org.slf4j - Unresolved requirement: Import-Package: org.slf4j when starting bundle in Kura Emulator 从OSGI命令提示符运行OSGI捆绑包:导入包缺少约束 - Running OSGI bundle from OSGI command prompt :Import-package missing constraint 如何修复 Eclipse RCP 中的“缺少约束:Import-Package:”和“Require-Bundle” - How to fix "Missing Constraint: Import-Package:" and "Require-Bundle" in Eclipse RCP
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM