RE: [picocontainer-dev] Ambiguity resolution?

--- Jörg Schaible <[email protected]>

> > Yes, but in this case child integer is not masking
> > parent - it got different key. So IMHO this shall
> > produce ambiguity.
> 
> No. The parent is only requested if the child
> container cannot resolve the dep (note, this is
> different for a collection). In this case the child
> is requested for an arbitrary Integer instance ...
> and it can provide one. So no ambiguity. The key is
> only considered if the type of two components *in
> the same* container match.

so you mean that ambiguous resolution is given only 
if there are ambiguous components on certain level? 

the question is, whther this is correct behavour - 
I would prefer that same kind of resolution by type
for whatever puprose. 


another issue is with testMoreWeirdness - adapter 
keyed with desired class wins  over others while
resolving by class - only on same level, or in 
parent too? 


regards,


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


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

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

    http://xircles.codehaus.org/manage_email