Jonathan Robie wrote:
Martin Ritchie wrote:
Are you suggesting writting a new Configuration API for the Java client?
No - Java JMS is the high level API for the Java client. Note that one
of the possible directions I suggested is to provide a way for other
languages to support the Java JMS properties files. The other route I
suggested is a configuration API.
I should point out the properties files that JMS uses are not part of
the JMS standard and the syntax of the entries is quite qpid specific.
FWIW, the way gsim and I have discussed dealing with configuration is to
provide a reasonable text based syntax for specifying an
address/destination that is just a name plus additional sender/producer
or consumer/receiver options. This should permit some consistency in
client configuration across languages and be usable via JNDI from Java.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
