Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Gemini » [Solved] Blueprint installation on another server (Jboss AS 7)(Blueprint installation on another server (Jboss AS 7))
[Solved] Blueprint installation on another server (Jboss AS 7) [message #989722] Fri, 07 December 2012 07:47 Go to next message
eis - is currently offline eis -
Messages: 16
Registered: September 2012
Junior Member
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]

Report message to a moderator

Re: Blueprint installation on another server (Jboss AS 7) [message #989726 is a reply to message #989722] Fri, 07 December 2012 07:56 Go to previous messageGo to next message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
The Blueprint extender is provided by the Gemini Blueprint extender bundle which you also need to install and start.
Re: Blueprint installation on another server (Jboss AS 7) [message #989733 is a reply to message #989726] Fri, 07 December 2012 08:15 Go to previous messageGo to next message
eis - is currently offline eis -
Messages: 16
Registered: September 2012
Junior Member
I thought the extender was only about Spring-specific extensions and not needed for blueprint. But ok, I've installed and started that too. Now, I'm seeing these as registered services:

- org.eclipse.gemini.blueprint.extender.internal.support.NamespacePlugins@3edb8d45
- org.eclipse.gemini.blueprint.extender.internal.support.NamespacePlugins@3edb8d45
- org.eclipse.gemini.blueprint.extender.internal.support.NamespacePlugins@741f7b5a
- org.eclipse.gemini.blueprint.extender.internal.support.NamespacePlugins@741f7b5a

but nothing else related to gemini blueprint, my services are still missing. Further suggestions?

[Updated on: Fri, 07 December 2012 08:19]

Report message to a moderator

Re: Blueprint installation on another server (Jboss AS 7) [message #989740 is a reply to message #989733] Fri, 07 December 2012 08:30 Go to previous messageGo to next message
eis - is currently offline eis -
Messages: 16
Registered: September 2012
Junior Member
Ok, I needed to add spring-asm and spring-expression as well. Now I am able to see my service. Yay!
Re: Blueprint installation on another server (Jboss AS 7) [message #989742 is a reply to message #989740] Fri, 07 December 2012 08:39 Go to previous messageGo to next message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
Phew - that's a relief!
Re: Blueprint installation on another server (Jboss AS 7) [message #1059495 is a reply to message #989740] Sun, 19 May 2013 17:44 Go to previous message
Alexandru Muntean is currently offline Alexandru Muntean
Messages: 1
Registered: May 2013
Junior Member
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]

Report message to a moderator

Previous Topic:Gemini Naming 1.0.2.RELEASE is now available
Next Topic:Combining Persistence Bundles
Goto Forum:
  


Current Time: Sun Aug 31 04:28:47 EDT 2014

Powered by FUDForum. Page generated in 0.01708 seconds