It does sound like a good idea, doesn't it?
To really make it work you'd have to redesign quite a lot of Windsor
internals.
For example dependency resolvers use DependencyInfo argument which is
not present when you resolve the root component.
If you want to have a look at implementing this I'm happy to accept your
pull request :)
Krzysztof
On 30/03/2011 8:48 PM, Cameron Harris wrote:
Hi all,
Is there a way of using subresolvers (such as CollectionResolver) on
the initial call to container.Resolve<T>()? Resolve only seems to work
if something is directly registered with the container.
https://gist.github.com/894190
On that example, I would like line 44 to work in a similar way to how
sub-dependencies are resolved when calling Resolve<Test>(), and return
a collection of all IPerson to me. Is there something I can do to make
that work, or another way of resolving through subresolvers directly
on the container? I had a look at going through
Kernel.Resolver.Resolve(..), but it required parameters that I didn't
know how to provide.
*Note that this isn't for use with CollectionResolver, because for
that I could always call ResolveAll - CollectionResolver is just an
example*
Thanks!
Cameron
--
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.
--
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.
