I noticed that the management package is being built against a different version of the RemoteMBeanServer interface than the one in the main codebase (there's a separate jar in the tools directory). There's a comment in the build file saying that this is because "RemoteMBeanServer is not available in the JBossMX project yet".
Trying to build against the actual class causes a compilation error because the "instantiate" methods from MBeanServer aren't implemented by the "LocalConnector" inner class of ManagementBean.
Would it be OK to add these so it compiles against the server module?
On closer inspection, it seems that the current RemoteMBeanServer now extends MBeanServer (unlike the version that is being compiled against), so a better option would sbe to change the connector instance in ManagementBean to an MBeanServer and remove the whole LocalConnector inner class and the extra unnecessary delegation (and 250 lines of code).
Any objections?
-- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
