Closed robj-applied closed 3 years ago
@robj-applied I would say that this is a poor design choice on my side. I used some tried to mimic some NServiceBus APIs in this behavior but I didn't take into account that for the router, it actually makes sense to connect to more than one.
I'll include support for this in the next release.
@SzymonPobiega That's great news, thank you.
Hi @SzymonPobiega when is V4 due to be released? This feature would be very useful. Thanks
Hi. Sorry to be late with this one but this feature has been shipped in 3.9.0
@SzymonPobiega Great, thanks Szymon.
Hi, apologies if I've misunderstood something here, but given the following code:
Only
router2
's routes would be registered in the endpoint. Anything that I think I've set up forrouter1
would result in aNo destination specified...
message.Presumably this is because this line
var router2 = routing.ConnectToRouter(Router2Name);
overwrites this linevar router1 = routing.ConnectToRouter(Router1Name);
?If I'm correct, just wondering is this by design or is it a bug?
In our useage of
NServiceBus.Router
we've come across a few occassions where we've had to roll our own solution for achieving this and it'd be great if it could be changed.Thanks in advance for taking a look. If I'm wrong or have misunderstood, then great - just let me know.
Thanks, Rob