MBean goals

The main motivation was to make the use of jConfig much easier in a J2EE application.
Actually the usage was simple right from the beginning but changing the configuration was
difficult. In former times we had the config.xml inside our ear file. Therefore we had to build a
new ear file each time the configuration had changed. Doing so during the development is easy.
But if you are at the customer and you only want to deploy the ear file, then you are running into
great difficulties.

Once we got familiar with JBoss and the usage of JMX and MBeans, it was clear that it was
exactly what we needed for jConfig. Now our lives are simple again when it comes to
deployment and administration of the configurations.

The configuration is outside the ear file (and in the conf-dir of JBoss where all the other
conf-files are). Together with the new auto-reload feature of jConfig1.3 it is just a matter of
opening the file, change the line(s) and save it. It will be reloaded automatically and there is
not even a need for restarting the server.

Use the MBean and your sysadmin will like you a bit more (don't expect that a sysadmin will
ever love you as a developer).