Chris-
Separate queues is a good approach. Additionally, it doesn't sound like
you need to do a network of brokers here. Stand-alone brokers and a
simple Camel route running inside the producer broker could handle the
content-based router requirement where you want messages sent to a
Thanks for the quick response. The content-based router seems to be good
for messages going only one way. However, in this scenario, when the
messages go out, the enumeration services need to reply to them at a
designated temp queue (at least that is my understanding of the
request/reply model in
Sorry, I must have glazed over the request-reply requirement. You can
still do it with a Camel route, you don't want to use Camel's default
request-reply behavior, which assumes one hop.
- Portal Producing Broker (set ReplyTo) - Camel route Content Based
Router (ignore ReplyTo) - Destination
