I deal with this by making my own facility that adds the ServiceBusFacility to the container at the right time.
On Jun 5, 9:41 am, Ayende Rahien <[email protected]> wrote: > Oh, so go ahead and change those > > On Fri, Jun 5, 2009 at 12:36 PM, Simone Busoli <[email protected]>wrote: > > > The problem is that, in the bootstrapper, ConfigureBusFacility is too early > > because the container isn't there yet, and the configuration on the facility > > is readonly, while ConfigureContainer is too tale because the facility has > > already been registered and it has complained that the config wasn't there. > > > On Fri, Jun 5, 2009 at 18:31, Ayende Rahien <[email protected]> wrote: > > >> You can modify the windsor.Configuration, IIRC > > >> On Fri, Jun 5, 2009 at 12:29 PM, Simone Busoli > >> <[email protected]>wrote: > > >>> I've come up with this to configure the bus: > >>> var host = new DefaultHost(); > >>> host.Start(FluentBootStrapper > >>> .WithBus(1, 5, endpoint, loadBalancer) > > >>> .Receiving(Message.Named(typeof(MyMessage).Namespace).FromEndpoint(producerEndpoint))); > > >>> The problem is that I had to change stuff inside AbstractBootstrapper and > >>> DefaultHost because I didn't find a way to add the configuration to the > >>> container before the facility is registered. Any idea? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
