Gordon Sim wrote:
I'm suggesting that the createQueue()/createTopic() behaviour be configured through a flag/mode on the connection and that when jndi is used to obtain a connection factory the value of that flag/mode could be different based on the context factory in use.
Ah, I understand now. That sounds like it would work. I think the question just boils down to whether we need to support addresses and binding URLs in use side by side or not (either in the same file or on the same connection).
It would seem the benefit to not supporting side by side usage is that we encourage a cleaner switchover, i.e. you go straight from the old to the new in a single step rather than having to prefix everything until you've eliminated all occurrences of the old syntax. Whereas supporting the old and new syntax side by side would allow a more incremental migration, but would require a second cleanup step at the end when you have only ADDR prefixed usages remaining.
From an implementation perspective neither option is particularly onerous. My impulse is probably to lean towards the clean switchover and not mixing usages, however I believe others have expressed the opposite view, maybe they could comment on the reasons?
--Rafael --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
