As part of the move to using POJO's we have lost some of the functionality we get from mbeans being redeployed on changes to the configuration. Since all the configuration is in one file we have to decide how best to replace this functionality. As it stands now we deploy a directory structure that looks as follows: | |-- META-INF | | `-- jbm-beans.xml | |-- jbm-configuration.xml | |-- jgroups.jar | |-- mina-core.jar | |-- slf4j-api-1.4.3.jar | `-- slf4j-log4j12.jar | At the minute any changes to the jbm-configuration.xml file will force a redeploy (albeit there is a bug in JBoss 5 Beta 3 and it doesnt work). However i think we should go for the following deployment configuration: deploy as an actual archive, which would have the same structure as above apart from the jbm-configuration.xml file which we would put in the conf dir. We then implement our own redeployment of changes to the config file, and also support multiple configuration files. This means that users can ship apps with a built in configuration file specific to the app. thoughts? PS Ive already implemented this on my local machine so not to much work would be involved. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117370#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...