[ https://jira.jboss.org/jira/browse/JBAS-7874?page=com.atlassian.jira.plug... ] Scott Marlow updated JBAS-7874: ------------------------------- Fix Version/s: JBossAS-6.0.0.M3 (was: JBossAS-6.0.0.M4) Description: The following unit test classes reference RMIAdaptor: - ClusterCacheTester (will be addressed by JBAS-7872) - DeploymentServiceUnitTestCase (verifyMBean method) - JMXInvokerUnitTestCase (update or remove) - RMIAdaptorUnitTestCase (update or remove) - JMXConnectorUnitTestCase (change to test our newly registered jmx connector) - BindingServiceUnitTestCase (update) - DRMTestCase (update or remove) - DistributedStateTestCase (update or remove) - authorization-jmx-invoker-service.xml (in testsuite) - securejmx-invoker-service.xml (in testsuite) was: The following unit test classes reference RMIAdaptor: - ClusterCacheTester (will be addressed by JBAS-7872) - DeploymentServiceUnitTestCase (verifyMBean method) - JMXInvokerUnitTestCase (update or remove) - RMIAdaptorUnitTestCase (update or remove) - JMXConnectorUnitTestCase (change to test our newly registered jmx connector) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7874?page=com.atlassian.jira.plug... ] Scott Marlow commented on JBAS-7874: ------------------------------------ Handle not serializable errors: <Nihility> smarlow: here is what i am thinking, you could add an option to your jmx connector thing <Nihility> to filter mbeaninfo of non serializable stuff <Nihility> to do that all you would have to do is create a delegate of mbeanserver <Nihility> and on a call to getMbeanInfo <Nihility> execute similar code that is in StripMOdelMBeanInfoPolicy * smarlow looking at StripMOdelMBeanInfoPolicy <Nihility> all it does is do a copy of mbean attribute inf <Nihility> so yeah the delegate of mbeanserver would be passed to the jmx connector <smarlow> so, we are leaving the unserializable class reference out in the copying? <Nihility> yeah the problem is with the way the implementaito of jmx works <smarlow> cool, sounds doable. I added the error handling in jmxconnector. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira