Quantcast
Channel: VMware Communities : Discussion List - vSphere Client SDK
Viewing all articles
Browse latest Browse all 2218

virgo says 'javax.annotation' constraint missing even though it was deployed

$
0
0

Below is the log showing that javax.annotation bundle was started

 

[2016-03-04T13:20:46.975-08:00] [INFO ] fs-watcher                    <HD0001I> Hot deployer processing 'CREATED' event for file 'javax.annotation-api-1.2.jar'.
[2016-03-04T13:20:46.975-08:00] [INFO ] fs-watcher                    <> ApplicationDeploying path 'D:\sdk\vsphere-client-sdk\server\pickup\javax.annotation-api-1.2.jar'.
[2016-03-04T13:20:47.148-08:00] [INFO ] fs-watcher                    <> Processing installing event for bundle 'javax.annotation-api' version '1.2.0'
[2016-03-04T13:20:47.207-08:00] [INFO ] fs-watcher                    <DE0000I> Installing bundle 'javax.annotation-api' version '1.2.0'.
[2016-03-04T13:20:47.207-08:00] [INFO ] fs-watcher                    <> Calculating missing dependencies of bundle(s) 'javax.annotation-api_1.2.0'
[2016-03-04T13:20:47.207-08:00] [INFO ] fs-watcher                    <> The dependencies of '[javax.annotation-api_1.2.0]' are '[javax.annotation-api_1.2.0]'
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Processing installed event for bundle 'javax.annotation-api:1.2.0' in region 'org.eclipse.virgo.region.user'
[2016-03-04T13:20:47.208-08:00] [INFO ] iLogServiceListener@30575b9e  <> Bundle javax.annotation-api_1.2.0, BundleEvent INSTALLED
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <DE0001I> Installed bundle 'javax.annotation-api' version '1.2.0'.
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Thread context class loader 'BundleDelegatingClassLoader for [Virgo Kernel Deployer (org.eclipse.virgo.kernel.deployer)]' popped and set to 'BundleDelegatingClassLoader for [Virgo Kernel Deployer (org.eclipse.virgo.kernel.deployer)]'
[2016-03-04T13:20:47.208-08:00] [INFO ] iLogServiceListener@30575b9e  <> Bundle javax.annotation-api_1.2.0, BundleEvent RESOLVED
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Thread context class loader 'BundleDelegatingClassLoader for [Virgo Kernel Deployer (org.eclipse.virgo.kernel.deployer)]' pushed and set to 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]'
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Thread context class loader 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]' popped and set to 'BundleDelegatingClassLoader for [Virgo Kernel Deployer (org.eclipse.virgo.kernel.deployer)]'
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Thread context class loader 'BundleDelegatingClassLoader for [Virgo Kernel Deployer (org.eclipse.virgo.kernel.deployer)]' pushed and set to 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]'
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Thread context class loader 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]' pushed and set to 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]'
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Adding signal 'org.eclipse.virgo.kernel.install.artifact.internal.AbstractInstallArtifact$StateMonitorSignal@133e88ff' for bundle 'javax.annotation-api_1.2.0 [366]'
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <DE0004I> Starting bundle 'javax.annotation-api' version '1.2.0'.
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Non-Spring DM powered bundle 'javax.annotation-api_1.2.0 [366]' has started. Driving signals '[org.eclipse.virgo.kernel.install.artifact.internal.AbstractInstallArtifact$StateMonitorSignal@133e88ff]'.
[2016-03-04T13:20:47.208-08:00] [INFO ] start-signalling-5            <> Driving signal 'org.eclipse.virgo.kernel.install.artifact.internal.AbstractInstallArtifact$StateMonitorSignal@133e88ff'
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Thread context class loader 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]' popped and set to 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]'
[2016-03-04T13:20:47.208-08:00] [INFO ] iLogServiceListener@30575b9e  <> Bundle javax.annotation-api_1.2.0, BundleEvent STARTED
[2016-03-04T13:20:47.208-08:00] [INFO ] start-signalling-5            <> Thread context class loader 'KernelBundleClassLoader: [bundle=com.vmware.vpshere.client.scheduledopsservice_6.0.0]' pushed and set to 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]'
[2016-03-04T13:20:47.208-08:00] [INFO ] fs-watcher                    <> Thread context class loader 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]' popped and set to 'BundleDelegatingClassLoader for [Virgo Kernel Deployer (org.eclipse.virgo.kernel.deployer)]'
[2016-03-04T13:20:47.208-08:00] [INFO ] start-signalling-5            <DE0005I> Started bundle 'javax.annotation-api' version '1.2.0'.
[2016-03-04T13:20:47.208-08:00] [INFO ] start-signalling-5            <> Thread context class loader 'KernelBundleClassLoader: [bundle=javax.annotation-api_1.2.0]' popped and set to 'KernelBundleClassLoader: [bundle=com.vmware.vpshere.client.scheduledopsservice_6.0.0]'

 

 

But here it says that the it is missing

 

[2016-03-04T13:22:46.567-08:00] [ERROR] fs-watcher                    <DE0002E> Installation of bundle 'org.glassfish.jersey.core.jersey-common' version '2.22.1' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'org.glassfish.jersey.core.jersey-common' at version '2.22.1': Cannot resolve: org.glassfish.jersey.core.jersey-common    Resolver report:        An Import-Package could not be resolved. Resolver error data <Import-Package: javax.annotation; version="[1.2.0,2.0.0)">. Caused by missing constraint in bundle <org.glassfish.jersey.core.jersey-common_2.22.1>             constraint: <Import-Package: javax.annotation; version="[1.2.0,2.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.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225)  at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79)  at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380)  at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289)  at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49)  at java.lang.Thread.run(Unknown Source)

 

 

Any ideas how I can get around this?


Viewing all articles
Browse latest Browse all 2218

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>