I'm really happy that we are playing in this direction, because I think
adopting the DI model, if we really adopt it fundamentally, will tend to
improve our modularity and clarify dependencies.
On the choice of Guice, I have concerns. From my perspective Spring is more
mature, well-documented and tested, has a more open contribution model, and
is in wider use amongst a broader community. Plus we have at least two
committers that are using it in other settings.
I understand some of the aversion to the XML configuration. Still XML can
be readily manipulated both manually and automatically during installation;
I hope we won't be asking users to modify distributed code in order, for
example, to add plugins or to swap a rendering model implementation.
--a.
- Re: svn commit: r539786 - /roller/branches/roller_guice/re... Anil Gangolli
-