Hi Ioannis,
Good point, but, for instance, if Karaf requires Aries Blueprint (only
for the namespace handler), it doesn't mean that we can't use another
Blueprint implementation (like Gemini). Pushing namespace handlers out
of the topic, it's already possible to use Gemini instead of Aries.
So, even if Karaf use Blueprint internally, it doesn't mean that you
can't use (from an user perspective) another implementations or framework.
Regards
JB
On 01/17/2014 10:55 AM, Ioannis Canellos wrote:
From my point of view blueprint is fine. It does simplify things a lot
and our users do use it. That doesn't mean that Karaf needs to use it
too.
Decoupling Karaf from blueprint, not only allows Karaf to have a
smaller footprint, but also allows provides more flexibility since
Karaf could be used with different versions/implementations of
Blueprint etc.
So this is actually a "step forward".
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
