Simplify QMan configuration (QPID-1411) : QMan is now an MBean itself!

[Andrea Gazzarini <a....@gmail.com>]

Hi all, according to what is described on QPID-1411 I'm going (tomorrow
morning) to submit the latest patch of QMan. Here are the new features : ***
CONFIGURATION *** 1) QMan configuration file schema has been changed so its
no longer possible to define type & access mode mappings. The reason is that
QMan must have a set of predefined mappings in order to work correctly and
it makes no sense to let the user configure them. That's applicable for type
mappings (association between a code and a management type i.e. 1 - Uint8)
and acces mode mappings (association between a code and an access mode i.e.
1 - RC). The only thing that you can configure is the broker(s) data (host,
port, virtual host, username, connection pool). 2) QMan bundle comes in this
version with no configuration file. org/apache/qpid/management/config.xml
has been removed : you can supply your own configuration file (containing
the broker(s) you want to connect) via command line using the option
-Dqman-config=<filename>. Note that this option is valid even if you are
using QMan deployed on an Application Server. If this option is missing QMan
starts without any connected broker. Later you can use its administration
interface in order to connect it with broker(s) **** QMAN ADMINISTRATION /
MANAGEMENT INTERFACE **** With this version QMan is itself an MBean and
therefore it has an administration / management interface. So if you are
using JConsole or JBoss JMX Console now you can see another MBean under the
Q-MAN domain (Q-MAN: Type=Service). At the moment there's only one available
operation called addBroker(...) that let's you connect QMan with a broker.
When you invoke that operation you can have one of the followinf scenarios :
- an exception (wrapped by MBeanException) called BrokerConnectionException
: a connection can't be esyabilished. - an exception (wrapped by
MBeanException) called BrokerAlreadyConnectedException : the broker is
already connected. - success : the broker is now connected and after just a
moment you should see events & objects coming from connected broker. Any
comment / suggestion would be appreciated...I'd need some suggestions about
other operations that should be part of QMan administration interface (stop,
start, removeBroker, wtc wtc Regards, Andrea