| [Solved] Blueprint installation on another server (Jboss AS 7) [message #989722] |
Fri, 07 December 2012 07:47  |
Eclipse User |
|
|
|
We have been using Aries Blueprint in JBoss as7, and are now checking out implications if we'd use Gemini Blueprint instead.
Now, with Aries, to get blueprint one needs to install bundles aries-util, aries-proxy and aries-blueprint, and things work after that. It seems that for gemini blueprint, at least the following bundles needs to be installed:
- aopalliance
- commons-logging
- spring-core
- spring-aop
- spring-beans
- spring-context
- gemini-blueprint-io
- gemini-blueprint-core
I have installed the above and now I can activate the blueprint bundle, but seems blueprint container is still not created, as I cannot see any blueprint-related services added into my OSGi context. Are there additional steps I need to take? I'm using the code that should be standard blueprint code, which is working with aries blueprint, with the addition of changing the manifest to point to org.eclipse.gemini.blueprint instead of org.osgi.service.blueprint. Is there something else I should do?
[Updated on: Fri, 07 December 2012 10:10] by Moderator |
|
|
|
|
|
|
| Re: Blueprint installation on another server (Jboss AS 7) [message #1059495 is a reply to message #989740] |
Sun, 19 May 2013 17:44  |
| Eclipse User |
|
|
|
Hi Eis,
Can you please tell me how did you fix this?:
20:51:44,547 INFO [org.eclipse.gemini.blueprint.extender.internal.boot.ChainActivator] (MSC service thread 1-8) Blueprint API detected; enabling Blueprint Container functionality
20:51:44,548 ERROR [org.jboss.osgi.framework] (MSC service thread 1-8) JBOSGI011026: Framework Error: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: org.eclipse.gemini.blueprint.extender:2.0.0.M02
at org.jboss.osgi.framework.spi.AbstractBundleAdaptor.start(AbstractBundleAdaptor.java:223) [jbosgi-framework-core-2.1.0.CR12.jar:2.1.0.CR12]
at org.jboss.osgi.framework.internal.StartLevelImpl.increaseStartLevel(StartLevelImpl.java:246) [jbosgi-framework-core-2.1.0.CR12.jar:2.1.0.CR12]
at org.jboss.osgi.framework.internal.FrameworkActive.createServiceValue(FrameworkActive.java:149) [jbosgi-framework-core-2.1.0.CR12.jar:2.1.0.CR12]
at org.jboss.osgi.framework.internal.FrameworkActive.createServiceValue(FrameworkActive.java:105) [jbosgi-framework-core-2.1.0.CR12.jar:2.1.0.CR12]
at org.jboss.osgi.framework.spi.AbstractIntegrationService.start(AbstractIntegrationService.java:60) [jbosgi-framework-core-2.1.0.CR12.jar:2.1.0.CR12]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_11]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_11]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]
Caused by: org.osgi.framework.BundleException: JBOSGI011253: Invalid bundle activator: org.eclipse.gemini.blueprint.extender.internal.boot.ChainActivator
at org.jboss.osgi.framework.spi.AbstractBundleAdaptor.start(AbstractBundleAdaptor.java:209) [jbosgi-framework-core-2.1.0.CR12.jar:2.1.0.CR12]
... 9 more
best regards,
Alex
[Updated on: Tue, 21 May 2013 13:57] by Moderator |
|
|
Powered by
FUDForum. Page generated in 0.08423 seconds
Home