great resource. thanks. Vish
On Sep 6, 7:53 pm, Krzysztof Koźmic <[email protected]> wrote: > http://docs.castleproject.org/Windsor.Extension-Points.ashx > > Feel free to contribute to it. > > Krzysztof > > On 07/09/2011 9:47 AM, Vish wrote: > > > > > > > > > awesome. Just the extension point i was looking for. Is there a wiki > > page on the extension points available in windsor and some info on > > when to use them? > > > Also, is there a link to this forum on the castle windsor site? > > > Thank You, > > Vish > > > On Sep 6, 5:41 pm, Krzysztof Koźmic<[email protected]> > > wrote: > >> I think ServiceOverrides are the preferred approach, as they can be > >> statically analysed. > > >> You can also try this approach I played with few years > >> back:http://kozmic.pl/2009/04/09/convention-based-dependency-injection-wit... > > >> Krzysztof > > >> On 07/09/2011 3:35 AM, Vish wrote: > > >>> Hi all, > >>> I was hoping to get some help with how to go about extending castle to > >>> automate the following. I am registering quite a few delegates with > >>> windsor. All delegate registrations are named. Some of the delegates > >>> have the same signatures. These delegates serve to satisfy some of the > >>> dependencies on my services. I want windsor to inject the right > >>> delegate into my services based on their signature which it already > >>> does. Since there are delegates with the same signature, I want the > >>> service to be injected with priority the delegate whose registration > >>> name matches the key for the dependency on the service. That is, if > >>> the delegate is registered with the name say 'GetAdminUsers', then if > >>> a service has a property dependency with the property name being > >>> 'GetAdminUsers', then the delegate named the same as the property > >>> should be prioritized to satisfy that dependency over other delegates > >>> with the same signature. I am currently having to do this using > >>> 'ServiceOverrides' at every service registration. Can windsor be > >>> extended to support this as a policy for all components rather than > >>> having to do this at every service registration? > >>> Thank You, > >>> Vish -- 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.
