Re: How to predict changes to ComponentModel, resulting from registration?

2011-05-21 Thread João Bragança
What if you registered it with a child container? Then you could somehow calculate the diff of what is resolvable. On May 20, 3:57 pm, Krzysztof Kozmic krzysztof.koz...@gmail.com wrote: Adam, That is an interesting idea. In Windsor v3 there's an interface called IDependencyInspector which

Re: How to predict changes to ComponentModel, resulting from registration?

2011-05-21 Thread Nimble
Hi That's a good idea, I think the component that is to be added temporarily would be in the child container then, right? I think that parent containers cannot resolve dependencies from child container (but children can resolve from parents), so I wouldn't get the entire story - I wouldn't

Re: How to predict changes to ComponentModel, resulting from registration?

2011-05-20 Thread Krzysztof Kozmic
Adam, That is an interesting idea. In Windsor v3 there's an interface called IDependencyInspector which you might use. It is called back from IHandler's (which implement IExposeDependencyInfo) with list of that handler's missing dependencies. I suppose you could then check type of those

How to predict changes to ComponentModel, resulting from registration?

2011-05-15 Thread Adam Langley
Team, I am curious, I would like to know, ahead of time, what result adding a new component to the MicroKernel will cause. For example, say I have a few components already registered, but some are currently 'awaiting dependencies'. I would like to know, if I were to add another component to the