Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Unexpected bundle installation behaviour(Greenpages clone app will not deploy...)
Unexpected bundle installation behaviour [message #643946] Wed, 08 December 2010 19:10 Go to next message
supercube Missing name is currently offline supercube Missing name
Messages: 11
Registered: December 2010
Junior Member
Hi,

After successfully installing Greenpages, I wanted to create my own app and created some new bundles that borrowed heavily from the Greenpages layout (a parent pom project, web and app bundles and a par). The only real difference between my app (called 'star') and greenpages is that instead of using Directory and Listing, this app uses my own objects. I have not yet added a JPA or db bundle..

When I try to deploy I get the following output. I used the (inappropriate) 2.3.0.RELEASE version tag for my bundles, so I don't understand why star.web' version '0.0.0' shows up on the second line...


[2010-12-08 11:47:16.026] TCP Connection(50)-127.0.0.1 <DE0000I> Installing par 'star' version '2.3.0.RELEASE'.
[2010-12-08 11:47:16.026] TCP Connection(50)-127.0.0.1 <DE0000I> Installing bundle 'star.web' version '0.0.0'.
[2010-12-08 11:47:16.135] TCP Connection(50)-127.0.0.1 <DE0002E> Installation of par 'star' version '2.3.0.RELEASE' failed. org.eclipse.virgo.kernel.deployer.core.DeploymentException: Unsatisfied dependency detected when expanding imports for [bundle 'star.web' version '0.0.0' in scope 'null', bundle 'star-2.3.0.RELEASE-synthetic.context' version '2.3.0.RELEASE' in scope 'star-2.3.0.RELEASE']
at org.eclipse.virgo.kernel.deployer.core.internal.ImportExpand ingTransformer.expandImports(ImportExpandingTransformer.java :116)
at org.eclipse.virgo.kernel.deployer.core.internal.ImportExpand ingTransformer.expandImportsOfBundlesInScopedPlan(ImportExpa ndingTransformer.java:89)
at org.eclipse.virgo.kernel.deployer.core.internal.ImportExpand ingTransformer$ImportExpandingTreeVisitor.visit(ImportExpand ingTransformer.java:76)
at org.eclipse.virgo.util.common.ThreadSafeArrayListTree.visit( ThreadSafeArrayListTree.java:165)
at org.eclipse.virgo.kernel.deployer.core.internal.ImportExpand ingTransformer.transform(ImportExpandingTransformer.java:58)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.in ternal.TransformationStage.doProcessTree(TransformationStage .java:55)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
at org.eclipse.virgo.kernel.deployer.management.StandardDeploye r.deploy(StandardDeployer.java:52)
at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenRetur n(ConvertingMethod.java:167)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:96)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:33)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntro spector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.jav a:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.jav a:262)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke (DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer .java:761)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RM IConnectionImpl.java:1427)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMI ConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOper ation.run(RMIConnectionImpl.java:1265)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOp eration(RMIConnectionImpl.java:1360)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConn ectionImpl.java:788)
at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.ja va:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTranspo rt.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TC PTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCP Transport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa dPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundl eDependenciesException: Unable to satisfy dependencies of bundle 'star-2.3.0.RELEASE-synthetic.context' at version '2.3.0.RELEASE': Import-Bundle with symbolic name 'star-2.3.0.RELEASE-star.web' in version range '[0.0.0, oo)' could not be satisfied
at org.eclipse.virgo.kernel.userregion.internal.importexpansion .ImportExpansionHandler.getBundlePackageImports(ImportExpans ionHandler.java:271)
at org.eclipse.virgo.kernel.userregion.internal.importexpansion .ImportExpansionHandler.getAdditionalPackageImports(ImportEx pansionHandler.java:236)
at org.eclipse.virgo.kernel.userregion.internal.importexpansion .ImportExpansionHandler.expandImports(ImportExpansionHandler .java:206)
at org.eclipse.virgo.kernel.userregion.internal.importexpansion .ImportExpansionHandler.expandImportsIfNecessary(ImportExpan sionHandler.java:174)
at org.eclipse.virgo.kernel.userregion.internal.importexpansion .ImportExpansionHandler.expandImports(ImportExpansionHandler .java:112)
at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsin gReflection(AopUtils.java:307)
at org.springframework.osgi.service.importer.support.internal.a op.ServiceInvoker.doInvoke(ServiceInvoker.java:58)
at org.springframework.osgi.service.importer.support.internal.a op.ServiceInvoker.invoke(ServiceInvoker.java:62)
at org.springframework.aop.framework.ReflectiveMethodInvocation .proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.support.DelegatingIntroductionInterc eptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at org.springframework.aop.support.DelegatingIntroductionInterc eptor.invoke(DelegatingIntroductionInterceptor.java:119)
at org.springframework.aop.framework.ReflectiveMethodInvocation .proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.osgi.service.util.internal.aop.ServiceTC CLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java :56)
at org.springframework.osgi.service.util.internal.aop.ServiceTC CLInterceptor.invoke(ServiceTCCLInterceptor.java:39)
at org.springframework.aop.framework.ReflectiveMethodInvocation .proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.osgi.service.importer.support.LocalBundl eContextAdvice.invoke(LocalBundleContextAdvice.java:59)
at org.springframework.aop.framework.ReflectiveMethodInvocation .proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.support.DelegatingIntroductionInterc eptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at org.springframework.aop.support.DelegatingIntroductionInterc eptor.invoke(DelegatingIntroductionInterceptor.java:119)
at org.springframework.aop.framework.ReflectiveMethodInvocation .proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke( JdkDynamicAopProxy.java:202)
at $Proxy63.expandImports(Unknown Source)
at org.eclipse.virgo.kernel.deployer.core.internal.ImportExpand ingTransformer.expandImports(ImportExpandingTransformer.java :107)
... 45 common frames omitted

[2010-12-08 11:47:16.135] TCP Connection(50)-127.0.0.1 <DE0003E> Install failed for bundle 'star.web' version '0.0.0'.
[2010-12-08 11:47:16.151] TCP Connection(50)-127.0.0.1 <DE0003E> Install failed for par 'star' version '2.3.0.RELEASE'.
Re: Unexpected bundle installation behaviour [message #643949 is a reply to message #643946] Wed, 08 December 2010 19:22 Go to previous messageGo to next message
Dmitry Sklyut is currently offline Dmitry Sklyut
Messages: 272
Registered: January 2010
Senior Member
Can you please share MANIFEST.MF of the web bundle with us?

Regards,
Dmitry
Re: Unexpected bundle installation behaviour [message #643953 is a reply to message #643949] Wed, 08 December 2010 19:45 Go to previous messageGo to next message
supercube Missing name is currently offline supercube Missing name
Messages: 11
Registered: December 2010
Junior Member
Manifest-Version: 1.0
Import-Bundle: com.springsource.org.apache.taglibs.standard;version="[
1.1.2,1.3)"
Bundle-Version: 2.3.0.RELEASE
Tool: Bundlor 1.0.0.RELEASE
Bundle-Name: Star Web
Import-Library: org.springframework.spring;version="[3.0, 3.1)"
Bundle-ManifestVersion: 2
Bundle-SymbolicName: star.web
Web-ContextPath: star
Import-Package: org.springframework.beans.factory.annotation;version="
[3.0.0, 3.1.0)",org.springframework.stereotype;version="[3.0.0, 3.1.0
)",org.springframework.web.bind.annotation;version="[3.0.0, 3.1.0)",o
rg.springframework.web.servlet.mvc.annotation;version="[3.0.0, 3.1.0)
",org.springframework.web.servlet.view.freemarker;version="[3.0.0, 3.
1.0)",star;version="[2.3.0)"
  • Attachment: MANIFEST.MF
    (Size: 0.71KB, Downloaded 66 times)
Re: Unexpected bundle installation behaviour [message #643954 is a reply to message #643953] Wed, 08 December 2010 19:50 Go to previous messageGo to next message
supercube Missing name is currently offline supercube Missing name
Messages: 11
Registered: December 2010
Junior Member
To be clear, the MANIFEST.MF in my previous reply is from my star.web bundle.

I am deloying a star par with project references to star.web and star.app, similar to Greenpages..
Re: Unexpected bundle installation behaviour [message #643955 is a reply to message #643953] Wed, 08 December 2010 19:51 Go to previous messageGo to next message
Dmitry Sklyut is currently offline Dmitry Sklyut
Messages: 272
Registered: January 2010
Senior Member
Is anything out there that exports star;version="[2.3.0)"?

Looks like a missing import that for some reason virgo is not able to give you an exact reason.

I am assuming that your app bundle exports "star" package.

Try this:
1. delete par from virgo (pickup I presume).
2. drop your app bundle into pickup
2.1 did that deploy properly
3. drop you web bundle into pickup
3.1. did that deploy properly

Dmitry
Re: Unexpected bundle installation behaviour [message #643992 is a reply to message #643955] Thu, 09 December 2010 00:08 Go to previous messageGo to next message
supercube Missing name is currently offline supercube Missing name
Messages: 11
Registered: December 2010
Junior Member
Is anything out there that exports star;version="[2.3.0)"?
No

I am assuming that your app bundle exports "star" package?
Yes. MANIFEST.MF from star.app bundle:

Manifest-Version: 1.0
Export-Package: star;version="2.3.0.RELEASE"
Bundle-Vendor: SpringSource Inc.
Bundle-Version: 2.3.0.RELEASE
Tool: Bundlor 1.0.0.RELEASE
Bundle-Name: Star App
Bundle-ManifestVersion: 2
Bundle-SymbolicName: star.app
Import-Package: org.springframework.stereotype;version="[3.0, 3.1)"


I created a PAR project in eclipse, put my star.app bundle in it and tried to install it to the server. Below is an exceprt from the logs.

The 'star.internal' package mentioned in the error is indeed in my star.app and I have the following in my module-context.xml:
<context:component-scan base-package="star.internal"/>


[2010-12-08 17:39:43.918] TCP Connection(4)-127.0.0.1 o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener Processing installing event for par 'starAppPar' version '2.3.0.RELEASE'
[2010-12-08 17:39:43.933] TCP Connection(4)-127.0.0.1 org.eclipse.virgo.medic.eventlog.default DE0000I Installing par 'starAppPar' version '2.3.0.RELEASE'.
[2010-12-08 17:39:43.933] TCP Connection(4)-127.0.0.1 o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener Processing installing event for bundle 'starAppPar-2.3.0.RELEASE-star.app' version '2.3.0.RELEASE'
[2010-12-08 17:39:43.933] TCP Connection(4)-127.0.0.1 org.eclipse.virgo.medic.eventlog.default DE0000I Installing bundle 'starAppPar-2.3.0.RELEASE-star.app' version '2.3.0.RELEASE'.
[2010-12-08 17:39:43.964] TCP Connection(4)-127.0.0.1 o.e.v.k.u.internal.importexpansion.ImportExpansionHandler Import-Library and/or Import-Bundle header found. Original manifest:
Manifest-Version: 1.0
Import-Bundle: starAppPar-2.3.0.RELEASE-star.app
Bundle-Version: 2.3.0.RELEASE
Bundle-ManifestVersion: 2
Module-Scope: starAppPar-2.3.0.RELEASE
Bundle-SymbolicName: starAppPar-2.3.0.RELEASE-synthetic.context


[2010-12-08 17:39:43.964] TCP Connection(4)-127.0.0.1 o.e.v.k.u.internal.importexpansion.ImportExpansionHandler Found definition for bundle with symbolic name 'starAppPar-2.3.0.RELEASE-star.app' and version range '[0.0.0, oo)': Manifest-Version: 1.0
Bundle-Vendor: SpringSource Inc.
Bundle-Version: 2.3.0.RELEASE
Tool: Bundlor 1.0.0.RELEASE
Bundle-Name: Star App
Bundle-ManifestVersion: 2
Bundle-SymbolicName: starAppPar-2.3.0.RELEASE-star.app
Module-Scope: starAppPar-2.3.0.RELEASE
Import-Package: star.internal


[2010-12-08 17:39:43.964] TCP Connection(4)-127.0.0.1 o.e.v.k.u.internal.importexpansion.ImportExpansionHandler Updated manifest:
Manifest-Version: 1.0
Bundle-Version: 2.3.0.RELEASE
Bundle-ManifestVersion: 2
Module-Scope: starAppPar-2.3.0.RELEASE
Bundle-SymbolicName: starAppPar-2.3.0.RELEASE-synthetic.context


[2010-12-08 17:39:43.964] TCP Connection(4)-127.0.0.1 o.e.virgo.kernel.userregion.internal.quasi.DependencyCalcula tor Calculating missing dependencies of bundle(s) 'starAppPar-2.3.0.RELEASE-star.app_2.3.0.RELEASE'
[2010-12-08 17:39:45.324] TCP Connection(4)-127.0.0.1 org.eclipse.virgo.medic.eventlog.default ME0003I Dump 'serviceability\dump\2010-12-08-17-39-980' generated
[2010-12-08 17:39:45.324] TCP Connection(4)-127.0.0.1 org.eclipse.virgo.medic.eventlog.default DE0002E Installation of par 'starAppPar' version '2.3.0.RELEASE' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundl eDependenciesException: Unable to satisfy dependencies of bundle 'starAppPar-2.3.0.RELEASE-star.app' at version '2.3.0.RELEASE': Cannot resolve: starAppPar-2.3.0.RELEASE-star.app
Resolver report:
An Import-Package could not be resolved. Caused by missing constraint in bundle <starAppPar-2.3.0.RELEASE-star.app_2.3.0.RELEASE>
constraint: <Import-Package: star.internal; version="0.0.0">

at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiResolveStage.process(QuasiResolveStage.java:45)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
at org.eclipse.virgo.kernel.deployer.management.StandardDeploye r.deploy(StandardDeployer.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenRetur n(ConvertingMethod.java:167)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:96)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:33)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntro spector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.jav a:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.jav a:262)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke (DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer .java:761)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RM IConnectionImpl.java:1427)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMI ConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOper ation.run(RMIConnectionImpl.java:1265)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOp eration(RMIConnectionImpl.java:1360)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConn ectionImpl.java:788)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.ja va:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTranspo rt.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TC PTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCP Transport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa dPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

[2010-12-08 17:39:45.324] TCP Connection(4)-127.0.0.1 o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener Processing install failed event for bundle 'starAppPar-2.3.0.RELEASE-star.app' version '2.3.0.RELEASE'
[2010-12-08 17:39:45.339] TCP Connection(4)-127.0.0.1 org.eclipse.virgo.medic.eventlog.default DE0003E Install failed for bundle 'starAppPar-2.3.0.RELEASE-star.app' version '2.3.0.RELEASE'.
[2010-12-08 17:39:45.339] TCP Connection(4)-127.0.0.1 o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener Processing install failed event for par 'starAppPar' version '2.3.0.RELEASE'
[2010-12-08 17:39:45.339] TCP Connection(4)-127.0.0.1 org.eclipse.virgo.medic.eventlog.default DE0003E Install failed for par 'starAppPar' version '2.3.0.RELEASE'.
[2010-12-08 17:39:45.339] TCP Connection(4)-127.0.0.1 org.eclipse.virgo.medic.eventlog.default DE0500E Unable to install application from URI 'file:/C:/virgo-web-server-2.1.0.RELEASE/stage/starAppPar.pa r'. Cannot satisfy constraints for bundle 'starAppPar-2.3.0.RELEASE-star.app' version '2.3.0.RELEASE'. Cannot resolve: starAppPar-2.3.0.RELEASE-star.app
Resolver report:
An Import-Package could not be resolved. Caused by missing constraint in bundle <starAppPar-2.3.0.RELEASE-star.app_2.3.0.RELEASE>
constraint: <Import-Package: star.internal; version="0.0.0">
. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundl eDependenciesException: Unable to satisfy dependencies of bundle 'starAppPar-2.3.0.RELEASE-star.app' at version '2.3.0.RELEASE': Cannot resolve: starAppPar-2.3.0.RELEASE-star.app
Resolver report:
An Import-Package could not be resolved. Caused by missing constraint in bundle <starAppPar-2.3.0.RELEASE-star.app_2.3.0.RELEASE>
constraint: <Import-Package: star.internal; version="0.0.0">

at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiResolveStage.process(QuasiResolveStage.java:45)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
at org.eclipse.virgo.kernel.deployer.management.StandardDeploye r.deploy(StandardDeployer.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenRetur n(ConvertingMethod.java:167)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:96)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:33)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntro spector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.jav a:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.jav a:262)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke (DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer .java:761)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RM IConnectionImpl.java:1427)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMI ConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOper ation.run(RMIConnectionImpl.java:1265)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOp eration(RMIConnectionImpl.java:1360)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConn ectionImpl.java:788)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.ja va:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTranspo rt.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TC PTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCP Transport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa dPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

[2010-12-08 17:39:45.339] TCP Connection(4)-127.0.0.1 org.eclipse.virgo.kernel.deployer.management.StandardDeploye r Exception filtered from JMX invocation org.eclipse.virgo.kernel.deployer.core.DeploymentException: Dependency satisfaction failed
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:274)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
at org.eclipse.virgo.kernel.deployer.management.StandardDeploye r.deploy(StandardDeployer.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenRetur n(ConvertingMethod.java:167)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:96)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:33)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntro spector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.jav a:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.jav a:262)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke (DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer .java:761)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RM IConnectionImpl.java:1427)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMI ConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOper ation.run(RMIConnectionImpl.java:1265)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOp eration(RMIConnectionImpl.java:1360)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConn ectionImpl.java:788)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.ja va:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTranspo rt.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TC PTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCP Transport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa dPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundl eDependenciesException: Unable to satisfy dependencies of bundle 'starAppPar-2.3.0.RELEASE-star.app' at version '2.3.0.RELEASE': Cannot resolve: starAppPar-2.3.0.RELEASE-star.app
Resolver report:
An Import-Package could not be resolved. Caused by missing constraint in bundle <starAppPar-2.3.0.RELEASE-star.app_2.3.0.RELEASE>
constraint: <Import-Package: star.internal; version="0.0.0">

at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiResolveStage.process(QuasiResolveStage.java:45)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
... 35 common frames omitted
Re: Unexpected bundle installation behaviour [message #644404 is a reply to message #643992] Fri, 10 December 2010 23:03 Go to previous messageGo to next message
supercube Missing name is currently offline supercube Missing name
Messages: 11
Registered: December 2010
Junior Member
I copied the star.app and star.web jars from eclipse's target folders to the the virgo web server pickup folder, changing them to .par files. I did not get any deployment errors but I did get version 0.0.0 messages in the logs (see below). The admin console shows version 0.0.0 PARS successfully installed also.

http://localhost/star is a 404 error page.

Here is the MANIFEST from star.app PAR file and the logged deployment messages.

MANIFEST.MF:

Manifest-Version: 1.0
Export-Package: star;version="2.3.0.RELEASE"
Bundle-Classpath: .
Built-By: supercube
Tool: Bundlor 1.0.0.RELEASE
Bundle-Name: Star App
Created-By: Apache Maven
Bundle-Vendor: SpringSource Inc.
Bundle-Version: 2.3.0.RELEASE
Build-Jdk: 1.6.0_21
Bundle-ManifestVersion: 2
Import-Package: org.springframework.stereotype;version="[3.0, 3.1)"
Bundle-SymbolicName: star.app
Archiver-Version: Plexus Archiver


Deployment Logs:

[2010-12-10 16:51:21.996] fs-watcher <DE0000I> Installing par 'star.web-2.3.0.RELEASE' version '0.0.0'.
[2010-12-10 16:51:22.058] fs-watcher <DE0001I> Installed bundle 'star.web-2.3.0.RELEASE-0-synthetic.context' version '0.0.0'.
[2010-12-10 16:51:22.058] fs-watcher <DE0001I> Installed par 'star.web-2.3.0.RELEASE' version '0.0.0'.
[2010-12-10 16:51:22.074] fs-watcher <DE0004I> Starting par 'star.web-2.3.0.RELEASE' version '0.0.0'.
[2010-12-10 16:51:22.074] fs-watcher <DE0004I> Starting bundle 'star.web-2.3.0.RELEASE-0-synthetic.context' version '0.0.0'.
[2010-12-10 16:51:22.074] start-signalling-3 <DE0005I> Started bundle 'star.web-2.3.0.RELEASE-0-synthetic.context' version '0.0.0'.
[2010-12-10 16:51:22.090] start-signalling-3 <DE0005I> Started par 'star.web-2.3.0.RELEASE' version '0.0.0'.
Re: Unexpected bundle installation behaviour [message #644624 is a reply to message #644404] Mon, 13 December 2010 14:19 Go to previous messageGo to next message
Dmitry Sklyut is currently offline Dmitry Sklyut
Messages: 272
Registered: January 2010
Senior Member
Is there any reason why you changed extension of the file to ".par"?

"par" is just one of deployment formats supported by Virgo.

Virgo is more than happy to deploy regular bundles, bundelised web applications and regular war files.

Try the same without changing the extension as it will confuse deployer.

Regards
Re: Unexpected bundle installation behaviour [message #644649 is a reply to message #644624] Mon, 13 December 2010 15:47 Go to previous messageGo to next message
supercube Missing name is currently offline supercube Missing name
Messages: 11
Registered: December 2010
Junior Member
I dropped the star-app.jar successfully and saw the right version deployed:

[2010-12-13 09:35:50.981] fs-watcher <HD0001I> Hot deployer processing 'CREATED' event for file 'star.app-2.3.0.RELEASE.jar'.
[2010-12-13 09:35:51.059] fs-watcher <DE0000I> Installing bundle 'star.app' version '2.3.0.RELEASE'.
[2010-12-13 09:35:51.153] fs-watcher <DE0001I> Installed bundle 'star.app' version '2.3.0.RELEASE'.
[2010-12-13 09:35:51.168] fs-watcher <DE0004I> Starting bundle 'star.app' version '2.3.0.RELEASE'.
[2010-12-13 09:35:51.309] start-signalling-4 <DE0005I> Started bundle 'star.app' version '2.3.0.RELEASE'.


However, the star-wepp.war does not deploy successfully. (The direcotry listed in the error "Unable to read bundle at 'file:/C:/virgo-web-server-2.1.0.RELEASE/...' looks to contain an exploded copy of star-web) :

[2010-12-13 09:37:18.262] fs-watcher <HD0001I> Hot deployer processing 'CREATED' event for file 'star.web-2.3.0.RELEASE.war'.
[2010-12-13 09:37:18.621] fs-watcher <DE0000I> Installing bundle 'star.web-2.3.0.RELEASE' version '0.0.0'.
[2010-12-13 09:37:19.871] fs-watcher <ME0003I> Dump 'serviceability\dump\2010-12-13-09-37-668' generated
[2010-12-13 09:37:19.887] fs-watcher <DE0002E> Installation of bundle 'star.web-2.3.0.RELEASE' version '0.0.0' failed. java.lang.RuntimeException: failed to install bundle in side state
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiInstallStage$InstallVisitor.visit(QuasiInstallStag e.java:77)
at org.eclipse.virgo.util.common.ThreadSafeArrayListTree.visit( ThreadSafeArrayListTree.java:149)
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiInstallStage.process(QuasiInstallStage.java:49)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSyste mListener.deploy(HotDeploymentFileSystemListener.java:174)
at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSyste mListener.onChange(HotDeploymentFileSystemListener.java:78)
at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners( FileSystemChecker.java:245)
at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystem Checker.java:166)
at org.eclipse.virgo.kernel.deployer.hot.WatchTask.run(WatchTas k.java:58)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.osgi.framework.BundleException: Unable to read bundle at 'file:/C:/virgo-web-server-2.1.0.RELEASE/work/org.eclipse.vi rgo.kernel.deployer_2.1.0.RELEASE/staging/global/bundle/star .web-2.3.0.RELEASE/0.0.0/star.web-2.3.0.RELEASE.war/'
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQ uasiFramework.doInstall(StandardQuasiFramework.java:117)
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQ uasiFramework.install(StandardQuasiFramework.java:102)
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiInstallStage$InstallVisitor.visit(QuasiInstallStag e.java:70)
... 17 common frames omitted
Caused by: java.lang.IllegalArgumentException: null
at org.eclipse.osgi.service.resolver.VersionRange.<init>(VersionRange.java:82)
at org.eclipse.osgi.internal.resolver.StateBuilder.getVersionRa nge(StateBuilder.java:532)
at org.eclipse.osgi.internal.resolver.StateBuilder.addImportPac kages(StateBuilder.java:271)
at org.eclipse.osgi.internal.resolver.StateBuilder.createImport Packages(StateBuilder.java:250)
at org.eclipse.osgi.internal.resolver.StateBuilder.createBundle Description(StateBuilder.java:99)
at org.eclipse.osgi.internal.resolver.StateObjectFactoryImpl.cr eateBundleDescription(StateObjectFactoryImpl.java:32)
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQ uasiFramework.doInstall(StandardQuasiFramework.java:112)
... 19 common frames omitted

[2010-12-13 09:37:19.887] fs-watcher <DE0003E> Install failed for bundle 'star.web-2.3.0.RELEASE' version '0.0.0'.
[2010-12-13 09:37:19.887] fs-watcher <HD0002E> Hot deploy failed for file 'star.web-2.3.0.RELEASE.war'. java.lang.RuntimeException: failed to install bundle in side state
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiInstallStage$InstallVisitor.visit(QuasiInstallStag e.java:77)
at org.eclipse.virgo.util.common.ThreadSafeArrayListTree.visit( ThreadSafeArrayListTree.java:149)
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiInstallStage.process(QuasiInstallStage.java:49)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSyste mListener.deploy(HotDeploymentFileSystemListener.java:174)
at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSyste mListener.onChange(HotDeploymentFileSystemListener.java:78)
at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners( FileSystemChecker.java:245)
at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystem Checker.java:166)
at org.eclipse.virgo.kernel.deployer.hot.WatchTask.run(WatchTas k.java:58)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.osgi.framework.BundleException: Unable to read bundle at 'file:/C:/virgo-web-server-2.1.0.RELEASE/work/org.eclipse.vi rgo.kernel.deployer_2.1.0.RELEASE/staging/global/bundle/star .web-2.3.0.RELEASE/0.0.0/star.web-2.3.0.RELEASE.war/'
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQ uasiFramework.doInstall(StandardQuasiFramework.java:117)
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQ uasiFramework.install(StandardQuasiFramework.java:102)
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiInstallStage$InstallVisitor.visit(QuasiInstallStag e.java:70)
... 17 common frames omitted
Caused by: java.lang.IllegalArgumentException: null
at org.eclipse.osgi.service.resolver.VersionRange.<init>(VersionRange.java:82)
at org.eclipse.osgi.internal.resolver.StateBuilder.getVersionRa nge(StateBuilder.java:532)
at org.eclipse.osgi.internal.resolver.StateBuilder.addImportPac kages(StateBuilder.java:271)
at org.eclipse.osgi.internal.resolver.StateBuilder.createImport Packages(StateBuilder.java:250)
at org.eclipse.osgi.internal.resolver.StateBuilder.createBundle Description(StateBuilder.java:99)
at org.eclipse.osgi.internal.resolver.StateObjectFactoryImpl.cr eateBundleDescription(StateObjectFactoryImpl.java:32)
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQ uasiFramework.doInstall(StandardQuasiFramework.java:112)
... 19 common frames omitted
Re: Unexpected bundle installation behaviour [message #644650 is a reply to message #644649] Mon, 13 December 2010 15:53 Go to previous messageGo to next message
Dmitry Sklyut is currently offline Dmitry Sklyut
Messages: 272
Registered: January 2010
Senior Member
Should have seen it before...

You have an invalid version range specified in the import of star package:
star;version="[2.3.0)"

// should be something like this

star;version="[2.3.0, 3)"


You were missing upper bound in the version range.

Dmitry
Re: Unexpected bundle installation behaviour [message #644957 is a reply to message #644650] Tue, 14 December 2010 23:59 Go to previous message
supercube Missing name is currently offline supercube Missing name
Messages: 11
Registered: December 2010
Junior Member
Thanks for that - star.web is finally deploying without errors.
http://localhost:8080/star is still returning a 404 but I need to do a bit of digging to figure out what exactly is going on...
Previous Topic:Virgo milestone 4 has shipped
Next Topic:Virgo integration with ECF remote services
Goto Forum:
  


Current Time: Tue Oct 21 08:58:16 GMT 2014

Powered by FUDForum. Page generated in 0.03070 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software