I was having the same problem and decided to go digging in the code for a
solution. In Rhino.ServiceBus.Impl.AbstractRhinoServiceBusConfiguration I
noticed the AddMessageModule<TModule>() method. This adds the specified
message module type to the configuration. Once added, the module will
automatically be registered with the DI container if you haven't done so
already.
The method can be invoked from the ConfigureBusFacility method in your
bootstrapper:
protected override void ConfigureBusFacility(
AbstractRhinoServiceBusConfiguration configuration )
{
configuration.AddMessageModule<MyMessageModule>();
base.ConfigureBusFacility( configuration );
}
After that my message module works as expected.
--
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rhino-tools-dev/-/U5ao5vc68mQJ.
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.