Architecting multi queue / multi topic subscriber component

[alinaqvi]

May I ask what is your main motivation for wanting different message-handlers per destination? Is it because of the data types of the messages arriving on those topics? Or is it something about controlling the handler context for each topic or flow? Depending on those reasons, my recommendations would vary.
Cheers,
kov

So lets say I am building component1(java app)
component1 receives OrderCommands from gui( topic/for/guicommands ) and ExchangeGW(topic/for/exchg_gw_commands).
gui can send us a new order-request and gw can send us an order-fill-response. Both of these are of type OrderCommands but I need to know if the msg came from gui or exchg_gw to raise an error incase its of incorrect type.

We also have price updates coming into component1. These are of completely different type so I need to route them to correct deserializer etc.

So there umpteen scenarios all over our app suite where we need to know which msg came from which topic.

Thanks,