On 11/15/2013 04:29 PM, Flavio Baronti wrote:
Thanks for your suggestion. I tried to implement it, but I did not get the behaviour I'd like. If I understood correctly, you suggested to create as many MessageConsumer instances as topics, and connect every consumer to the same queue, each time specifying a different binding key. What happens in this situation is that, for each message which matches with at least one of the bindings of the queue, one of the consumers is called, in a round-robin fashion. So the first consumer is called for the first matching message, the second consumer for the second message, and so on, with no relationship between the subject of the message and the intended topic of the consumer. If this is the expected behaviour, then I'm supposed to implement the matching logic in the application code, which I was trying to avoid (in the real application the topics are not always fully-specified, but often contain # or *).
Yes, you are right, I hadn't considered that properly. Sorry! --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
