Re: [picocontainer-dev] Simplify PIcoConatienr interface/ Refactor parameter[s]

Its most definitely a hack - am interested in an elegant successor.

The ParameterName interface is to allow a lazy lookup of a parameter  
name (arguably costly) without affecting performance.  The majority  
case for Pico will be looking up by type (as always), the minority  
use will be by parameter name.

Incidentally, we need to put in the binding annotations thing too,  
sooner or later.  It's in the same space:

     class CompA {
       public CompA(@JdbcUserName String name, @JdbcPassword String  
password) { }
     }

Dreadfully verbose, but definitely something a versatile embeddable  
container should do.

- Paul

On Nov 16, 2007, at 9:06 AM, peter royal wrote:

> On Nov 16, 2007, at 6:48 AM, Konstantin Priblouda wrote:
>> It seems to me that method:
>>   <T> ComponentAdapter<T>
>> getComponentAdapter(Class<T> componentType,
>> ParameterName componentParameterName);
>> on PicoContainer is a bit too much on main interface.
>>
>> So, why not simplify things a little?
>> (Of course this is not intendet to hold beta,
>> as parameters are functional now though not really
>> effective )
>
> +1, that looks like a weird paul-created method ;)
>
> -pete
>
> -- 
> (peter.royal|osi)@pobox.com - http://fotap.org/~osi
>


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

    http://xircles.codehaus.org/manage_email