Re: [picocontainer-dev] comments on injection

Give us patches dude, for both member injection and hooks - you mean  
@implementedBy(...) right ?

-ph

ps - be aware there are renames going on presently.

For one, I'm killing org.picocontainer.defaults.* class by class.  
Either moving them to elsewhere or deleting them as they've proven  
after four years to not be need at the current level of type-safety  
(exceptions)


On May 31, 2007, at 11:48 AM, Putrycz, Erik wrote:

> I moved most of my project to pico 2 and was hoping to use the new  
> injection but currently the only injection available is on methods…
>
> I’m not very keen on the method injection, it creates IMO often too  
> much verbose code whereas a member injection is quicker to write.  
> Often I don’t even need a getter and setter…
>
> However I think both would be nice to have.
>
> Any objection on adding member injection?
>
> I also think I figured out a way to inject members of an existing  
> object without modifying the container. I’ll see how that turns out.
>
>
> Last comment… I know this is very unpopular here but I’d be nice if  
> there was some kind of hook in Pico to be able to setup auto  
> registration of classes. Somekind of callback on getComponent –  
> when not found – would be nice.
>
>