Hi, I have made some progress with component registration. XML config does not support registering multiple interfaces, but it can be extended by facility: http://stackoverflow.com/questions/274220/does-castle-windsor-support-forwardedtypes-via-xml-configuration Now I am able to register message handler by config: <component id="MyComponent" type="WindsorTest1.MyDearComponent, WindsorTest1" service="WindsorTest1.IMyDearComponent, WindsorTest1"> <forward> <service>Rhino.ServiceBus.ConsumerOf`1 [[WindsorTest1.MyDearMessage, WindsorTest1]], Rhino.ServiceBus</ service> </forward> </component> And messages flow as expected. Hope this will help someone with configuration. Regarding the opinionation of software, I think rhino tools are a bit opinionated, but not too much. Browsing the sources shows how author's opinions evolved in time. My opinion is that windsor container dependency is unpleasant and encourages developers to use the container in an imperative way (by adding code to explicitly interact with the container), while for example in spring framework you can do more wiring externally by configuration, avoiding dependencies. But I'll give windsor more attention and maybe will change opinion about it in future. Second thing I don't like too much is heavy use of generics, this makes program structure very static and runtime configuration difficult - but this is my opinion, maybe a result of horrible memories of C++ programming with ATL and WTL. Best regards R
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
