Another problem I'm seeing with the change in interceptors is that the invocation context associated with attribute interceptors is using a copy of the ModelMBeanAttributeInfo descriptor, and this is what the ModelMBeanAttributeInterceptor is updating. However, the PersistenceInterceptor simply calls the ModelMBeanInvoker through its PersistentMBean.store() method to write out the changed values. However, the ModelMBeanInvoker attribute VALUE descriptors have not been modified, and so the current persistence manager implementation does not work. The cached attribute values are also local copies in the various interceptors. There is not any way to obtain the descriptor refence from the current ModelMBeanAttributeInfo as it only supports a getDescriptor() method which returns a copy of the descriptor. How has the ModelMBean persistence been tested?
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
