Re: [gatein-dev] A word about Exo kernel - MC integration
On Oct 8, 2009, at 6:11 PM, Christophe Laprun wrote:
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 agree with you but the API does not change with the current version
of GateIn 3.x as it will be Pico reimplemented (wrapping) the MC
engine. It is what we agreed. So that is invalid to me.
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...
It's an API, MC also has an API under the form of annotations (and
more if you want such as the aware interface), it's certainly less
intrusive, nevertheless that remains a *proprietary* API. So that's
more valid but still, does not make a real point.
We all know that MC is a wonderful piece of engineering and its
development took 4 years, so we expect it better than pico, aren't we ?
What I was asking for is for instance as things such as
1/ "as MC is a real state machine, it performs a better dependency
resolution, where Pico does not have a real notion of start/stop
lifecycle"
or
2/ "as MC is integrated with management, that would allow to provide
proper management of services within the EPP environment"
those would be valid argument to me.
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