Hey Kevin - I really think there's a better way to address your use case needs with ActiveMQ that would avoid the turnover of destinations. I would welcome the opportunity to help you figure that out.
With that said, if you want to implement your own "read-only" destination feature, it would be relatively easy to do with a Broker Filter. One concern I have is putting too much optional functionality directly into ActiveMQ - every option increases the complexity of ActiveMQ and makes it that much harder to maintain in general. "Separation of concerns" is a powerful tool. -- View this message in context: http://activemq.2283324.n4.nabble.com/Marking-a-destination-read-only-tp4691065p4691078.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
