Re: [picocontainer-dev] Re: the patch ?

--- Paul Hammant <[email protected]> wrote:

> There's still some functionality that
> ConfigParameter has that  
> BasicParameter does not, so I'll merge that in
> before deleting  
> (unless you want to do it Konstantin), 

What exactly do you mean?  The only difference is 
that config parameter  shops for strings by key
and utilizes xstream converters. Though dynamic
discovery for not yet registered classes would 
be fine. 

Merging this functionality would negate the need for
basic component parameter too (which was introduced 
to share common functionality) 


But it just comes to my mind - why not split parameter
into "by key" and "by class"  - this would greatly
simplify things inside:

ByKey: 
  - lookup by key, attempt conversion if string,
bomb if not found

ByType: lookup by type, bomb if ambiguous. do no
conversion (too dangerous for  implicit parameters) 

ByType-Parameter  will not be seen in outside, because
it usually comes into play  when automatic wiring is
specified. (but I think should be offered for sake of
simmetry) 

Or shall we say, that parameter is always by key? 
( and by type resolution shall be left to
instantiating adapters ) 




> You've made
> quite a powerful  
> feature that will be great in the core, even it the
> type-safety  
> police have heart attacks..

Nah, what type safety you are speaking of in
environment living by reflection? ;) 

----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/


      ____________________________________________________________________________________
Get easy, one-click access to your favorites. 
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs 

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

    http://xircles.codehaus.org/manage_email