<dmlloyd> don't do it this way
<dmlloyd> instead, implement it as a service
<dmlloyd> write a jboss-beans.xml which creates a...
<dmlloyd> ~~ smarlow javadoc RMIServerImpl
<javabot> smarlow: http://is.gd/aPe3U [JDK: javax.management.remote.rmi.RMIServerImpl]
<dmlloyd> and injects the MBeanServer from the MC
<dmlloyd> then for now just stick it into deploy/ (we can move it to an earlier bootstrap phase at a later time)
<Nihility> ~ javadoc RMIConnectorServer
<javabot> http://is.gd/4roR1 [JDK: javax.management.remote.rmi.RMIConnectorServer]
<dmlloyd> ah yeah
<smarlow> sure, that sounds better
<dmlloyd> taht's the better choice
<Nihility> we needed to do that anyway
<Nihility> this will make it easy to configure
<Nihility> which i like
<Nihility> also it lets us secure the connection
<dmlloyd> smarlow, so for now just a jboss-beans.xml will do it. Sometime later (M4) we can make a special domain-esque <jmx-connector-server .../> thing
<smarlow> dmlloyd: sounds great, thanks!