NServiceBus: Events, Multiple Inheritance, Handlers being called more than once per event -

I have some mysterious problems, which once correlated with events created through more than one event per event called Looks Inherent Inheritance

We are using only the interface for our messages and put it on to the NServiceBus.MessageInterfaces.MessageMapper.Reflection.MessageMapper () .BuildInstance () to use to do .

Our Interface:

IOperation Eligible - This includes basic operation information, members of this event work on things in a normal way. This incident is never raised directly.

ISpecificOperation Eligible - Inheritance IOperationOccured . It contains more specific information.

The problem is that when ISpecificOperationIckured is raised, handlers for IOperation Code> is called, HandlerXide for ISpecificOperation is called and then the message appears to be re-processed, then call the handler.

What am I misunderstanding? To call me once per event, handler for IOperationOccured and handler for the one time call ISpecificOperationIckured to call per event was.

I know the late reply but hopefully it will help others.

This happens when your different handlers are deployed in the same end point to ensure IOperation is appropriate and ISpecificOperation

Endpoint 1 (Arises IpecificOperationIccured)

< Li> Endpoint 2 (IOperation handles both secure and ISpecificOperation)

End point 1 Entries for membership will be included:

• OK for iOperation -> end point 2
• ensure ISpecificOperation -> end point 2

So when ISpecificOperation has been published, this afternoon it will be sent to Endpoint2. The recommended approach is to have different endpoint for different message types operation.

Endpoint 3 (ISPIC Operate Eligible) Arises

Endpoint 2 (Handles IOperation)

End Point 3 (Handles ISpecificOperation Eligible)