You pass the container in the constructor and you are done. On Mon, Oct 6, 2008 at 8:17 AM, josh robb <[EMAIL PROTECTED]> wrote:
> > On Sun, Oct 5, 2008 at 12:58 PM, Ayende Rahien <[EMAIL PROTECTED]> wrote: > > I committed the work, you can check the test here: > > > https://svn.castleproject.org/svn/castle/trunk/InversionOfControl/Castle.Windsor.Tests/HandlerSelectorsTestCase.cs > > As a bonus, it also deals with sub dependencies without any involvement > from > > me at all :-) > > Thoughts? > > As far as I am concerned, this move a lot of the business logic > extensions > > to the IHandlerSelector, and leave ISubDependencyResolver to deal with > > mostly parameters and other things that aren't handlers. > > Nice! - This is a really nice extension point. It seems a lot clearer > than using on the the existing extension points without really > changing the behavior of the container. > > The main problem I can see is wanting to use the container to resolve > components in a SelectorHandler (i.e. to obtain an application context > type thing). > > j. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
