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.
On Sat, Oct 4, 2008 at 11:44 PM, Ken Egozi <[EMAIL PROTECTED]> wrote:
> yess. will make things easier ...
>
> IHandler Select(string key, ...) ?
>
>
> On Sat, Oct 4, 2008 at 7:58 AM, josh robb <[EMAIL PROTECTED]> wrote:
>
>>
>> On Sat, Oct 4, 2008 at 11:15 AM, Ayende Rahien <[EMAIL PROTECTED]> wrote:
>> > No, the naming system itself.
>> > It will allow extension similar to this:
>> > public interface IDependencySelector
>> > {
>> > IHandler Select(Type type, IEnumerable<IHandler> handlers);
>> > }
>>
>> Oh - cool. Thats a really elegant solution.
>>
>> j.
>>
>>
>>
>
>
> --
> Ken Egozi.
> http://www.kenegozi.com/blog
> http://www.musicglue.com
> http://www.castleproject.org
> http://www.gotfriends.co.il
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
