Vinay,
Have integration tests as custom extension of the compliler. Than you'll
be able to refactor fearlessly.
It is possible to pass typed arguments elsewhere *explicitly*. With
typed factory you're being implicit on the call site and explicit on the
configuration, so it is not possible to do this unfortunately.
Good news though, is that writing custom selector and attaching it to a
factory as well as adding custom kinds of arguments (that is other than
named and typed) was also significantly improved in the 2.5 release.
You inherit from default selector, override GetArguments method and
there you can provide the arguments as typed instead of named.
HTH,
Krzysztof
On 20/07/2010 7:48 AM, Vinay Mandy wrote:
Hi.
I am very interested in using Typed Factory interfaces to resolve some
of my component dependencies. However, I do not like the fact that I
have to name the factory method arguments exactly the same as my
component's constructor parameters.
I find that this too fragile a binding because the compiler will not
be able to inform developers of a possible code break if they ever
change either the factory method argument or constructor parameter
name without also changing the other.
I guess that I could handle this myself by implementing my own
ITypedFactoryComponentSelector, but I was wondering if there were any
plans to provide this out of the box in the next official release
(2.5) of Windsor?
I noticed that there are already plans to include added support for
typed arguments in many other areas, why not here too?
Thanks.
--
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.
