Here I send you a patch that fix this behaviour. Regards.
On Wed, Nov 5, 2008 at 10:17 AM, Ayende Rahien <[EMAIL PROTECTED]> wrote: > No, it isn't okay, it should only return things that are implementing the > service > > > On Wed, Nov 5, 2008 at 3:15 PM, Germán Schuager <[EMAIL PROTECTED]>wrote: > >> Thanks for the hint. >> >> I've thought of that, but I didn't want to reference the >> Castle.Components.Validator assembly from where ArrayResolver lives. >> >> Besides this particular problem, is it ok that ResolveAll<T> returns every >> component that implements T even if they are registered with another >> service? >> >> ** >> On Wed, Nov 5, 2008 at 9:50 AM, Ayende Rahien <[EMAIL PROTECTED]> wrote: >> >>> Modify the array resolver to special case for this bit >>> >>> >>> On Wed, Nov 5, 2008 at 1:02 PM, Germán Schuager <[EMAIL PROTECTED]>wrote: >>> >>>> >>>> Hi, I'm following up to this post because I've been told that it was >>>> tagged as spam. >>>> >>>> Anyone on this? >>>> >>>> Thanks. >>>> >>>> On Nov 3, 1:09 pm, Germán Schuager <[EMAIL PROTECTED]> wrote: >>>> > Hi, >>>> > >>>> > I'm using the ArrayResolver that Hammet proposed herehttp:// >>>> hammett.castleproject.org/?p=257. >>>> > >>>> > Also, I'm registering IValidatorRunner (from >>>> > Castle.Components.Validator) in the container in this way: >>>> > >>>> > container.Register( >>>> > >>>> > >>>> Component.For<IValidatorRegistry>().ImplementedBy<CachedValidationRegistry>(), >>>> > >>>> > >>>> Component.For<IValidatorRunner>().ImplementedBy<ValidatorRunner>().LifeStyle.Transient >>>> > ) >>>> > >>>> > Besides this, I've some others components registered that implements >>>> > IValidationContributor (but are not registered with this service) >>>> > >>>> > The problem that I'm facing is that when an IValidatorRunner is being >>>> > resolved, the ArrayResolver tries to get every IValidationContributor >>>> > from the container in order to use the constructor with the following >>>> > signature: >>>> > >>>> > public ValidatorRunner(IValidationContributor[] contributors, >>>> > IValidatorRegistry registry) >>>> > >>>> > but I don't really want this behaviour. >>>> > Instead, I just want it to be resolved using the constructor with this >>>> > other signature: >>>> > >>>> > public ValidatorRunner(IValidatorRegistry registry) >>>> > >>>> > Questions: >>>> > 1. Is that Ok that ResolveAll returns components that implement >>>> > IValidationContributor but that are not registered using that service? >>>> > 2. Is there any way to specify my requirement when registering >>>> > IValidatorRunner? >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
resolveallfix.patch
Description: Binary data
