We'd need to think about the mbean interface as well; i.e .if we still want to expose a property via JMX attributes on the deployer then aggregating properties into beans doesn't help much. For the clustering properties I don't see any point in still exposing JMX setters for them; they shouldn't be changed after the deployer is started. Several of the clustering properties I'm tempted to pull out of the deployer anyway; they just set global defaults that can be overridden in jboss-web.xml. I could just make the defaults hard coded for a few rarely used ones (e.g. snapshotMode/Interval). I'd have done that already but I found out a major customer is actually using snapshotMode a lot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089824#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...