[gatein-dev] A word about Exo kernel - MC integration

[Christophe Laprun]

On Oct 8, 2009, at 2:31 PM, Julien Viet wrote:

> 1/ I agree with you that it is not acceptable to not have source code

+1

> 2/ I don't find this argument valid from my perspective, can you
> instead tell us what it would bring to use MC instead of pico

Less invasive DI framework. Better support for wiring of POJOs. For  
example, with the current implementation, I had to add a useless (from  
the code perspective) argument to my service constructor just to make  
sure that the service would be instantiated after some other one: real  
bad design!

I do agree that eating our own dog food is not a goal in itself but  
any DI framework that forces you to implement non-business interfaces  
and doesn't allow to explicit dependencies outside of your code cannot  
really call itself a real DI framework...

Cordialement / Best,
Chris

==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow JBoss Portal: http://jbossportal.blogspot.com / http://twitter.com/jbossportal
Follow me: http://metacosm.codepuccino.com / http://twitter.com/metacosm