Cheers,That's a result of a breaking change (which I admit somehow didn't get documented in breakingchages.txt, or at least not explicitly)
Basically this is part of the same change as with ResolveAll method on the container - Windsor will now respect the services a component exposes, whereas previously it was just looking at the implementation type.
So you get an empty array, because there is no component exposing SecondComponent (or any assignable type) as a service. The only service in the container, exposed by two components, is ITestComponent.
How to make it work again, depends on what the real scenario does, and what your intention for this is.
HTH, Krzysztof On 14/01/2012 5:56 AM, mynkow wrote:
As I promised here is the failing test. https://gist.github.com/1608359When you run the test an exception is thrown. I am not sure if all this stuff like facilities should be there to reproduce it but the important part is that is is failing. I also tried to swap the code as I did in the application but it is still failing.PS: May be I am doing something wrong? --You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-users/-/4bjZSNelf7oJ. 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.
<<inline: beghicfa.png>>
