Hi folks, I created a separate thread to ensure it gets the attention it deserves. The javax.jms.Destination provides a very poweful abstraction and we don't seem to fully utilize it. The JMS 1.1 introduced the Destination interface bcos they felt the Topic and Queue didn't cover all the use cases. Infact the prefered way is to use Destinations and not Topics or Queues. In the session interface there is no "createDestination" method. You can only lookup a destination via JNDI. This allows immense flexibility where you can create any type of destination hidden behind the interface.
But I see our implementation is centered around Topic and Queues (they are the first class citizens). As Godon pointed out in the BindingURL thread, we can use the Destination abstraction to cover a lot of the AMQP specific features. I think we should think about a proper strategy for subclassing the AMQDestination class to provide this extensible functionality. We can then influence the AMQP WG to make this a standard by submitting proposals to the JMS SIG. Regards, Rajith Attapattu Red Hat blog: http://rajith.2rlabs.com/
