Arnaud Simon wrote:
Even if it is part of AMQP there will be plenty of clients that want
to
use AMQP proper without using the management protocol. Everything in
the
client module gets bundled into a single jar that will be embedded in
any application that uses Qpid, so there is good reason to keep this
jar
and its dependencies as lightweight as possible.
I kind of agree but following this reasoning this would mean that we need a standalone jar for the jms client.
I'm not sure I follow. We *do* have a standalone jar for the jms client.
Or we did before the management stuff was put under client.
--Rafael
