This does seem to be sufficient and the persistent attribute testcase in the failing DeployXMBeanUnitTestCase is now working.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Tuesday, January 20, 2004 1:56 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Too many copies of model mbean info objects Is this enough as there are several places copies are being introduced: - AbstractMBeanInvoker.preRegister + This calls initAttributeContexts(info.getAttributes());, which makes a copy of the MBeanAttributeInfo[] - ModelMBeanInvoker.initAttributeContexts + This calls ctx.setDescriptor(info.getDescriptor()); which passes in a copy of Descriptor from the copy of the MBeanAttributeInfo obtained from the MBeanInfo. Therefore, all attribute sets are operating on copies of the MBeanAttributeInfo. Is adding info.setDescriptor(...) to the AbstractMBeanInvoker.setAttribute(Attribute) finally going to be enough? It looks like this might, I'll test it out. ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
