Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Communications Framework (ECF) » ECF container does not get activated with Gemini Blueprint
ECF container does not get activated with Gemini Blueprint [message #1005456] Fri, 25 January 2013 09:15 Go to previous message
Joerg Saini is currently offline Joerg Saini
Messages: 8
Registered: January 2013
Junior Member
We have been evaluating the Eclipse Communication Framework (ECF) with Declarative Services and Blueprint. While with DS works ok, when using Blueprint the ECF container does not work. All the required bundles for Blueprint have been installed:

- org.aopalliance
- org.apache.commons.logging
- org.eclipse.gemini.blueprint.core
- org.eclipse.gemini.blueprint.extender
- org.eclipse.gemini.blueprint.io
- org.springframework.aop
- org.springframework.asm
- org.springframework.beans
- org.springframework.context
- org.springframework.core
- org.springframework.expression

The blueprint appears as active but nothing gets published. Switching to DS (with the respective changes in the bean configuration under OSGI-INF and the manifest file) makes the ECF remote service available again. Is there something else we should do? We are seeing this even when modifying the examples found at http://git.eclipse.org (org.eclipse.ecf.examples.remoteservices.hello.ds.host and org.eclipse.ecf.examples.remoteservices.hello.ds.consumer) which work perfectly fine with DS.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic:ECF doesn't remember IM providers from one eclipse session to the next
Next Topic:ECF Generic server is connecting to the wrong host
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Tue May 21 02:46:44 EDT 2013

Powered by FUDForum. Page generated in 0.01546 seconds