Jonathan Robie wrote:
Rafael Schloming wrote:
There really are two separate configuration topics here: configuration
of the client (which is reasonable to do via JNDI) and configuration
of the broker (which nobody in their right mind would ever consider
doing via JNDI). It would probably be helpful clarify which one you
mean in a given context.
The Java JMS examples we use configure the broker - they set up queues
and bindings in the broker. What's our story here - is this something
that nobody in their right mind would actually do? If so, we might want
to change this in our examples once we provide better alternatives ....
Yes, this is pretty much insane since you need to separately specify
your broker schema for each client that connects, and if they don't all
match (e.g. one has a typo) then who knows what you'll end up getting.
It's a race where the first client to connect wins.
Not to mention it's woefully incomplete as a mechanism to configure the
broker, e.g. there is no way to delete the queues and bindings you
create this way.
In general you should have a single well documented schema for the
broker that is maintained separately from all the clients, and the
clients should be configured with the minimal information required to
connect to this schema, i.e. just the relevant queue or topic name.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
