Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » ArtifactGenerationException: Manifest ill-formed.(Virgo Web Server error deploying bundle with oracle driver )
ArtifactGenerationException: Manifest ill-formed. [message #645557] Fri, 17 December 2010 23:29 Go to next message
supercube Missing name is currently offline supercube Missing nameFriend
Messages: 11
Registered: December 2010
Junior Member
I created db bundle to connect to an Oracle database.

I added a dependency to the pom.xml:

<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc6</artifactId>
<version>11.2.0.1.0</version>
</dependency>

In my eclipse project, I can see the resulting ojdbc6-11.2.0.1.0.jar in my Maven Dependencies, and in that jar I can see the oracle.jdbc.OracleDriver.class

I added an import package for this driver to my template.mf that prodcued the following MANIFEST.MF:

Manifest-Version: 1.0
Bundle-Version: 2.3.0.RELEASE
Tool: Bundlor 1.0.0.RELEASE
Bundle-Name: Db
Bundle-ManifestVersion: 2
Bundle-Description: Star DataSource
Import-Package: javax.sql;version="0",oracle.jdbc;version="[11.2.0.1.0
, 11.2.0.1.0]",org.apache.commons.dbcp;version="[1.2.2.osgi, 1.2.2.os
gi]"
Bundle-SymbolicName: star.db

Maven successfully build/packages this project.

When I drop it into the virgo-web-server-2.1.0.RELEASE\pickup fiolder I get the following stack trace:

[2010-12-17 17:03:17.788] fs-watcher org.eclipse.virgo.medic.eventlog.default HD0001I Hot deployer processing 'CREATED' event for file 'star.db-2.3.0.RELEASE.jar'.
[2010-12-17 17:03:17.788] fs-watcher o.e.virgo.kernel.deployer.hot.HotDeploymentFileSystemListene r ApplicationDeploying path 'C:\virgo-web-server-2.1.0.RELEASE\pickup\star.db-2.3.0.RELE ASE.jar'.
[2010-12-17 17:03:17.788] fs-watcher o.e.v.k.i.artifact.internal.StandardArtifactIdentityDetermin er Error occurred while determining the type of an Artifact 'C:\virgo-web-server-2.1.0.RELEASE\pickup\star.db-2.3.0.RELE ASE.jar' with the bridge '$Proxy72'. org.eclipse.virgo.repository.ArtifactGenerationException: Manifest ill-formed.
at org.eclipse.virgo.kernel.artifact.bundle.BundleBridge.genera teArtifactDescriptor(BundleBridge.java:112)
at sun.reflect.GeneratedMethodAccessor55.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 $Proxy72.generateArtifactDescriptor(Unknown Source)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardA rtifactIdentityDeterminer.determineIdentity(StandardArtifact IdentityDeterminer.java:97)
at org.eclipse.virgo.kernel.install.artifact.internal.Delegatin gServiceRegistryBackedArtifactIdentityDeterminer.determineId entity(DelegatingServiceRegistryBackedArtifactIdentityDeterm iner.java:60)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardI nstallArtifactTreeInclosure.determineIdentity(StandardInstal lArtifactTreeInclosure.java:135)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardI nstallArtifactTreeInclosure.createInstallTree(StandardInstal lArtifactTreeInclosure.java:118)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :140)
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: java.lang.IllegalArgumentException: invalid format
at org.osgi.framework.Version.<init>(Version.java:140)
at org.osgi.framework.Version.parseVersion(Version.java:218)
at org.eclipse.virgo.util.osgi.VersionRange.<init>(VersionRange.java:78)
at org.eclipse.virgo.util.osgi.manifest.internal.BaseImported.g etVersion(BaseImported.java:48)
at org.eclipse.virgo.kernel.artifact.bundle.BundleBridge.applyI mportPackage(BundleBridge.java:166)
at org.eclipse.virgo.kernel.artifact.bundle.BundleBridge.genera teArtifactDescriptor(BundleBridge.java:96)
... 33 common frames omitted

[2010-12-17 17:03:17.850] fs-watcher o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener Processing installing event for bundle 'star.db-2.3.0.RELEASE' version '0.0.0'
[2010-12-17 17:03:17.850] fs-watcher org.eclipse.virgo.medic.eventlog.default DE0000I Installing bundle 'star.db-2.3.0.RELEASE' version '0.0.0'.
[2010-12-17 17:03:19.084] fs-watcher org.eclipse.virgo.medic.eventlog.default ME0003I Dump 'serviceability\dump\2010-12-17-17-03-850' generated
[2010-12-17 17:03:19.100] fs-watcher org.eclipse.virgo.medic.eventlog.default DE0002E Installation of bundle 'star.db-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 .db-2.3.0.RELEASE/0.0.0/star.db-2.3.0.RELEASE.jar/'
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: invalid format
at org.osgi.framework.Version.<init>(Version.java:140)
at org.osgi.framework.Version.parseVersion(Version.java:218)
at org.eclipse.osgi.service.resolver.VersionRange.<init>(VersionRange.java:87)
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-17 17:03:19.100] fs-watcher o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener Processing install failed event for bundle 'star.db-2.3.0.RELEASE' version '0.0.0'
[2010-12-17 17:03:19.100] fs-watcher org.eclipse.virgo.medic.eventlog.default DE0003E Install failed for bundle 'star.db-2.3.0.RELEASE' version '0.0.0'.
[2010-12-17 17:03:19.100] fs-watcher System.out java.lang.RuntimeException: failed to install bundle in side state
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiInstallStage$InstallVisitor.visit(QuasiInstallStag e.java:77)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.util.common.ThreadSafeArrayListTree.visit( ThreadSafeArrayListTree.java:149)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiInstallStage.process(QuasiInstallStage.java:49)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSyste mListener.deploy(HotDeploymentFileSystemListener.java:174)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSyste mListener.onChange(HotDeploymentFileSystemListener.java:78)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners( FileSystemChecker.java:245)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystem Checker.java:166)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.hot.WatchTask.run(WatchTas k.java:58)
[2010-12-17 17:03:19.100] fs-watcher System.out at java.lang.Thread.run(Thread.java:619)
[2010-12-17 17:03:19.100] fs-watcher System.out 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 .db-2.3.0.RELEASE/0.0.0/star.db-2.3.0.RELEASE.jar/'
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQ uasiFramework.doInstall(StandardQuasiFramework.java:117)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQ uasiFramework.install(StandardQuasiFramework.java:102)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiInstallStage$InstallVisitor.visit(QuasiInstallStag e.java:70)
[2010-12-17 17:03:19.100] fs-watcher System.out ... 17 more
[2010-12-17 17:03:19.100] fs-watcher System.out Caused by: java.lang.IllegalArgumentException: invalid format
[2010-12-17 17:03:19.100] fs-watcher System.out at org.osgi.framework.Version.<init>(Version.java:140)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.osgi.framework.Version.parseVersion(Version.java:218)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.osgi.service.resolver.VersionRange.<init>(VersionRange.java:87)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.osgi.internal.resolver.StateBuilder.getVersionRa nge(StateBuilder.java:532)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.osgi.internal.resolver.StateBuilder.addImportPac kages(StateBuilder.java:271)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.osgi.internal.resolver.StateBuilder.createImport Packages(StateBuilder.java:250)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.osgi.internal.resolver.StateBuilder.createBundle Description(StateBuilder.java:99)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.osgi.internal.resolver.StateObjectFactoryImpl.cr eateBundleDescription(StateObjectFactoryImpl.java:32)
[2010-12-17 17:03:19.100] fs-watcher System.out at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQ uasiFramework.doInstall(StandardQuasiFramework.java:112)
[2010-12-17 17:03:19.100] fs-watcher System.out ... 19 more
[2010-12-17 17:03:19.116] fs-watcher org.eclipse.virgo.medic.eventlog.default HD0002E Hot deploy failed for file 'star.db-2.3.0.RELEASE.jar'. 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 .db-2.3.0.RELEASE/0.0.0/star.db-2.3.0.RELEASE.jar/'
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: invalid format
at org.osgi.framework.Version.<init>(Version.java:140)
at org.osgi.framework.Version.parseVersion(Version.java:218)
at org.eclipse.osgi.service.resolver.VersionRange.<init>(VersionRange.java:87)
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: ArtifactGenerationException: Manifest ill-formed. [message #645581 is a reply to message #645557] Sat, 18 December 2010 07:34 Go to previous messageGo to next message
Hristo Iliev is currently offline Hristo IlievFriend
Messages: 156
Registered: May 2010
Location: Sofia, Bulgaria
Senior Member

The version seems to be invalid according to the specification:

digit ::= [0..9]
alpha ::= [a..zA..Z]
alphanum ::= alpha | digit
number ::= digit+

version ::= major( '.' minor ( '.' micro ( '.' qualifier )? )? )?
major ::= number
minor ::= number
micro ::= number
qualifier ::= ( alphanum | '_' | '-' )+

Therefore the range [11.2.0.1.0, 11.2.0.1.0] has to be changed to comply with the OSGi versions. The last part - qualifier cannot contain '.'

If you just remove .0 in the end - [11.2.0.1, 11.2.0.1] the bundle is deployed ok (provided there are bundles exporting the package).

[Updated on: Sat, 18 December 2010 07:39]

Report message to a moderator

Re: ArtifactGenerationException: Manifest ill-formed. [message #645585 is a reply to message #645581] Sat, 18 December 2010 10:32 Go to previous messageGo to next message
Glyn Normington is currently offline Glyn NormingtonFriend
Messages: 1222
Registered: July 2009
Senior Member
The diagnostics could have been better. The root cause:

Caused by: java.lang.IllegalArgumentException: invalid format
at org.osgi.framework.Version.<init>(Version.java:140)

should probably include the version in the exception message to give a better clue to the reason for the failure. I have raised bug 332886 against Equinox to improve this.
Re: ArtifactGenerationException: Manifest ill-formed. [message #646421 is a reply to message #645585] Thu, 23 December 2010 22:10 Go to previous messageGo to next message
supercube Missing name is currently offline supercube Missing nameFriend
Messages: 11
Registered: December 2010
Junior Member
Thanks for the help.

I installed a new version of the oracle driver in to my local maven repository, with a better version format of 11.2.1.0

I dropped this jar into my .../repository/usr folder too.

I added a dependency to my pom.xml:
<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc6</artifactId>
<version>11.2.1.0</version>
</dependency>

I updated my templae.mf to import this version. Here is my MANIFEST.MF:

Manifest-Version: 1.0
Bundle-Version: 2.3.0.RELEASE
Tool: Bundlor 1.0.0.RELEASE
Bundle-Name: Db
Bundle-ManifestVersion: 2
Bundle-Description: Star DataSource
Import-Package: com.jdbc;version="[11.2.1.0, 11.2.1.0]",javax.sql;vers
ion="0",org.apache.commons.dbcp;version="[1.2.2.osgi, 1.2.2.osgi]"
Bundle-SymbolicName: star.db


When I drop the star-db.jar into the pickup folder I still get errors with the imported packages in the jar:

[2010-12-23 16:07:01.278] fs-watcher org.eclipse.virgo.medic.eventlog.default DE0000I Installing bundle 'star.db' version '2.3.0.RELEASE'.
[2010-12-23 16:07:01.278] fs-watcher o.e.virgo.kernel.userregion.internal.quasi.DependencyCalcula tor Calculating missing dependencies of bundle(s) 'star.db_2.3.0.RELEASE'
[2010-12-23 16:07:02.496] fs-watcher org.eclipse.virgo.medic.eventlog.default ME0003I Dump 'serviceability\dump\2010-12-23-16-07-293' generated
[2010-12-23 16:07:02.512] fs-watcher org.eclipse.virgo.medic.eventlog.default DE0002E Installation of bundle 'star.db' version '2.3.0.RELEASE' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundl eDependenciesException: Unable to satisfy dependencies of bundle 'star.db' at version '2.3.0.RELEASE': Cannot resolve: star.db
Resolver report:
An Import-Package could not be resolved. Caused by missing constraint in bundle <star.db_2.3.0.RELEASE>
constraint: <Import-Package: com.jdbc; version="[11.2.1.0,11.2.1.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.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)

[2010-12-23 16:07:02.512] fs-watcher o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener Processing install failed event for bundle 'star.db' version '2.3.0.RELEASE'
[2010-12-23 16:07:02.512] fs-watcher org.eclipse.virgo.medic.eventlog.default DE0003E Install failed for bundle 'star.db' version '2.3.0.RELEASE'.
[2010-12-23 16:07:02.512] fs-watcher org.eclipse.virgo.medic.eventlog.default DE0500E Unable to install application from URI 'file:/C:/virgo-web-server-2.1.0.RELEASE/pickup/star.db-2.3. 0.RELEASE.jar'. Cannot satisfy constraints for bundle 'star.db' version '2.3.0.RELEASE'. Cannot resolve: star.db
Resolver report:
An Import-Package could not be resolved. Caused by missing constraint in bundle <star.db_2.3.0.RELEASE>
constraint: <Import-Package: com.jdbc; version="[11.2.1.0,11.2.1.0]">
. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundl eDependenciesException: Unable to satisfy dependencies of bundle 'star.db' at version '2.3.0.RELEASE': Cannot resolve: star.db
Resolver report:
An Import-Package could not be resolved. Caused by missing constraint in bundle <star.db_2.3.0.RELEASE>
constraint: <Import-Package: com.jdbc; version="[11.2.1.0,11.2.1.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.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)

[2010-12-23 16:07:02.528] fs-watcher System.out org.eclipse.virgo.kernel.deployer.core.DeploymentException: Dependency satisfaction failed
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:274)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSyste mListener.deploy(HotDeploymentFileSystemListener.java:174)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSyste mListener.onChange(HotDeploymentFileSystemListener.java:78)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners( FileSystemChecker.java:245)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystem Checker.java:166)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.hot.WatchTask.run(WatchTas k.java:58)
[2010-12-23 16:07:02.528] fs-watcher System.out at java.lang.Thread.run(Thread.java:619)
[2010-12-23 16:07:02.528] fs-watcher System.out Caused by: org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundl eDependenciesException: Unable to satisfy dependencies of bundle 'star.db' at version '2.3.0.RELEASE': Cannot resolve: star.db
[2010-12-23 16:07:02.528] fs-watcher System.out Resolver report:
[2010-12-23 16:07:02.528] fs-watcher System.out An Import-Package could not be resolved. Caused by missing constraint in bundle <star.db_2.3.0.RELEASE>
[2010-12-23 16:07:02.528] fs-watcher System.out constraint: <Import-Package: com.jdbc; version="[11.2.1.0,11.2.1.0]">
[2010-12-23 16:07:02.528] fs-watcher System.out
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.inte rnal.QuasiResolveStage.process(QuasiResolveStage.java:45)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
[2010-12-23 16:07:02.528] fs-watcher System.out at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
[2010-12-23 16:07:02.528] fs-watcher System.out ... 9 more
[2010-12-23 16:07:02.528] fs-watcher org.eclipse.virgo.medic.eventlog.default HD0002E Hot deploy failed for file 'star.db-2.3.0.RELEASE.jar'. 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.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.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundl eDependenciesException: Unable to satisfy dependencies of bundle 'star.db' at version '2.3.0.RELEASE': Cannot resolve: star.db
Resolver report:
An Import-Package could not be resolved. Caused by missing constraint in bundle <star.db_2.3.0.RELEASE>
constraint: <Import-Package: com.jdbc; version="[11.2.1.0,11.2.1.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)
... 9 common frames omitted
Re: ArtifactGenerationException: Manifest ill-formed. [message #646439 is a reply to message #646421] Fri, 24 December 2010 09:04 Go to previous message
Glyn Normington is currently offline Glyn NormingtonFriend
Messages: 1222
Registered: July 2009
Senior Member
This seems like a different issue. I suggest you look in the state dump using the admin console to see if there is any sign of an export for com.jdbc and what version it has.
Previous Topic:Questions running hibernate
Next Topic:password "admin" is not accepted for jmx remote authentication
Goto Forum:
  


Current Time: Sat Dec 07 02:40:00 GMT 2024

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

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

Back to the top