On Sun, 11 Nov 2001 21:05, Vincent Massol wrote:
> The most interesting part of Avalon for me is not the services but rather
> the fact that it uses best practice patterns and especially IOC. This is
> sooo important. Because on almost all my projects I have to mentor teams of
> developers who are very juniors and who 1/ have never programmed in java
> and 2/ have no experience with OOP/COP. Using Avalon gives them a
> documented framework that will force them to program properly.
>
> One of the big driver in favor of IOC for me is that it will lead to code
> that can easily be unit tested using Mock Objects (www.mockobjects.com)
> [and of course flexible and without to many dependencies - but that's why I
> can unit test it easily with mocks, i.e. isolate a portion of code from its
> domain (i.e. calling and caller classes)].
Hadn't thought of it in that way. You just convinced me that maybe I should
push to to have avalon/Framework adopted for our EJB stuff ;)
--
Cheers,
Pete
----------------------------------------
"Liberty means responsibility. That is
why most men dread it." - Locke
----------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
