Martin Ritchie wrote:
Your right I probably did but also ment that if you want a Queue Object then JNDI InitialContext gives that to you. Currently if you actually want the queue to be created on the broker in a pure JMS way then createConsumer(..) is the only way to go.
I think we need to support createQueue()/createTopic() for a number of reasons. First, it is part of the JMS specification, so I don't think we really have a choice. Second, there are existing usages, and I wouldn't want to discourage people from using the new format by saying it's not supported directly via createQueue()/createTopic(). Third, while the JMS specification does warn that the value passed in is vendor specific, its arguable that we don't actually care if a user wants to write code that is specific to a qpid client.
Finally, the actual issue with using it is that destinations are vendor specific configuration and if you're trying to remain vendor neutral then you shouldn't hardcode vendor specific configuration into your applications, however I think there are completely reasonable usages that don't hardcode configuration, e.g. passing a specification in from the command line wouldn't make your code at all vendor specific.
--Rafael --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
