Re: [picocontainer-dev] New Picocontainer-web ... defeating IoC made easier now :-(

>
> I don't see the point of all this to be honest :-)
>
> Even in the previous design the user could have gotten hold of the  
> reference to the container from the action, using the context lookup  
> key.   It has not changed in this respect.  It's a features of web  
> development that is inherently and potentially un-IoC.
>

true, but only if they had a handle on request, session etc. Actions  
do not typically, thus this is increased vulnerability..

> IMO we should avoid unnecessary complications and just put forward  
> the "best practice".   I mean - Pico also supports setter-injection  
> although that is known, if not well implemented, to leave objects in  
> an unknown state.   And even constructor-injection can be  
> implemented badly.  So, the bottom line is:  educate users but don't  
> complicate unnecessarily ;-)

Let us not go overboard then - keep the method signature simple, but  
move to the package solution Mike talked of.

- Paul



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email