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-with-castle-microkernelwindsor/
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.
