RE: [picocontainer-dev] [Paul?] DPC.initForConfig()

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

> Paul Hammant wrote on Tuesday, August 14, 2007 7:32
> AM:
> 
> > No, I think that's right. It means there are too
> many possibilities
> > rather than too few. 
> 
> Hmmm. I think I'm with Konstantin. Ambigous means
> for me, that there are too many *matching* deps and
> Pico does not know which to take. If no component
> matches, they're ignored and therefore I'd extpected
> UnsatisfiableDependenciesException also ... but just
> my 2 cents.

Anyway, why  config entries are in default container
at all?  They could live with APC ( and of course with

upcoming property / sysproperty / environment ) 

I must admit that I found this by mistake - I looked 
for cause of instable build of nano-groovy  - nodes 
are not test covered  and sometimes awkward
( relying on order/amount of parameters, not on names
)

There is more to be found ;) 

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


       
____________________________________________________________________________________
Yahoo! oneSearch: Finally, mobile search 
that gives answers, not web links. 
http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC

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

    http://xircles.codehaus.org/manage_email