Hi all,
we can have different kind of issue:
- Gemini Blueprint and Aries blueprint share the same blueprint
namespace, that's why you can deploy both in the same container (or you
can have side effect)
- it's quite the same between JPA, JTA, etc as Gemini and Aries provide
OSGi services (without properties) to the same interface (for instance
the JPA entity manager). However, it could world with some minor enhancement
- we don't have issue between Spring DM and Aries because they don't use
the same namespace
My 0.02$
Regards
JB
On 11/01/2011 04:25 PM, mikevan wrote:
Raman,
Can you describe the technical reason why you couldn't use camel, aries, and
gemini contexts in the same bundle? To my knowledge, aries and gemini both
leverage the osgi interfaces for osgi stuff. So, as long as the service is
consumed by the same context used by camel, shouldn't they work?
----- Original Message -----
From: "Raman Gupta [via Karaf]"<[email protected]>
To: "mikevan"<[email protected]>
Sent: Tuesday, November 1, 2011 11:06:36 AM
Subject: Re: Aries and Spring Co-Existance in Karaf
On 11/01/2011 10:30 AM, mikevan wrote:
Why can't Gemini work in Karaf?
You're right. I don't know if it will work. I should have said "it
doesn't work out of the box". If you decide to try it and get it
working I'd be interested in your features.xml.
I too have used Virgo extensively but have decided to move to Karaf
for my current project. But I'd definitely like to see Gemini on Karaf.
I believe your other scenario (camel, blueprint, spring contexts in
the same bundle) is not possible with Aries Blueprint, but is possible
with Gemini Blueprint.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
