How to configure MessageEndpointMapping by namespace in NServiceBus

Question

I am trying to configure my message endpoint mapping in my NServiceBus configuration by sending messages from different namespaces to different endpoints.

As such, I have configured the following in my web.config:

<MessageEndpointMappings>
    <add Messages="Company.Messages.Accounts" Endpoint="ServiceInput" />
    <add Messages="Company.Messages.Payments" Endpoint="ServiceInput" />
    <add Messages="Company.Messages.Cancellations" Endpoint="ServiceInput" />
    <add Messages="Company.Messages.Notifications" Endpoint="ServiceInput" />
</MessageEndpointMappings>

However, when my application starts, I receive the following exception:

Spring.Objects.PropertyAccessExceptionsException: PropertyAccessExceptionsException (1 errors); nested PropertyAccessExceptions are: [Spring.Core.TypeMismatchException: Cannot convert property value of type [System.Collections.Hashtable] to required type [System.Collections.IDictionary] for property 'MessageOwners'., Inner Exception: System.ArgumentException: Problem loading message assembly: Company.Messages.Payments ---> System.IO.FileNotFoundException: Could not load file or assembly 'Company.Messages.Payments' or one of its dependencies. The system cannot find the file specified. File name: 'Company.Messages.Payments'

What I find interesting is that it seems to have found Company.Messages.Accounts but failed on the second configured line. I thought that maybe it didn't like have them all go to the same endpoint, but changing this configuration to have them go different endpoints didn't change the error message I received.

What am I doing wrong? Is it not possible to segment messages by namespace (all I have seen is by type and by assembly)?

Thanks, Steve

Euryale

Answer 1

NSB only supports mapping of assemblies or individual types to endpoints. Namespaces are not supported, I suggest you split you message assembly into separate assemblies for each of your endpoints.

Quintin

Thanks Andreas. Someone on the NServiceBus email list suggested it was possible, but I couldn't seem to get it to work. Thanks for the definitive answer. ~Steve – Euryale

3.3.0 added support for namespaces as well – Scleroprotein

andreas. u should update this answer to reflect the new API. perhaps a link to doco – Hue

Answer 2

According to this page you can specify a type: http://docs.particular.net/nservicebus/messaging/message-owner

Specific types can be configured by using their qualified name: "namespace.type, assembly".

Swoop

Great to include link. I never read the pub sub example because I didn't need it yet, however I havn't seen that little tid-bit anywhere else in the docs. – Firenew

Answer 3

As of NServiceBus v3.3 namespaces can be used to filter message mappings

http://docs.particular.net/nservicebus/messaging/message-owner

Quintin

Perhaps the doco should also point out that NServiceBus (4.7 is the version I'm using!) also fails if I add the Image extension (*.dll in my case). Quite counter-intuitive! – Dowager

We have the note here: docs.particular.net/nservicebus/messaging/… Any ideas on have we can make it more clear? – Scleroprotein