I'm glad that helped. At a quick glance your new code looks pretty good.
The important thing was being able to only send the message to the "next"
broker so that your broker filter doesn't get called in an infinite loop
and your new code does this. Your new code is also much more efficient
than b
Thank you very much christopher.l.shannon.
Your reply helped me to solve the problem.
This is the new code (the modifications are in bold) for any one who may be
interested. Your critics are welcomed of course.
Regards,
public class MyBroker extends BrokerFilter {
public MyBroker(Broker ne
As you have found out you shouldn't try and use the JMS client api from
inside the broker, as that is for client code. I'm not entirely sure I
understand why you can't use advisory topics but if you want to send a
message to another destination from inside the broker there are lots of good
examples
Hello,
I was trying to implement an interceptor to log some events happening in the
broker. I want the events to be logged as messages in queue. Thus, the
monitoring client could access the log by consuming messages from that
queue.
(I didn't uses advisory topics because I want to dequeue treated
