Gordon Sim wrote:
On 12/15/2009 12:03 AM, Aidan Skinner wrote:
On Fri, Dec 11, 2009 at 9:20 AM, Martin Ritchie<[email protected]>
wrote:
What ever we do new JNDI, prefixing (which I find a tad strange) we
need to support both formats simultaneously in a single file to allow
users to migrate.
Mixing formats in one file seems unlikely. Wouldn't users change all
the urls in their file at once?
That would be my view also.
Using different context factories for the parsing seems like the best
solution to me. It does mean that users have to change code as well as
configuration when switching over.
I think they would only need to change code if they were passing binding
urls to createQueue()/createTopic(). If they were only passing straight
queue names (or topic names) then I don't think any change should be
necessary to their code. Unless of course I am missing something?
The semantics of createQueue("foo") depend on whether "foo" is
interpreted as an address or not. Under the current semantics this would
automatically declare the queue on the server. If interpreted as an
address, you would need to supply "foo; {create: always, assert:
always}" in order to get equivalent semantics.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
