I have forced cglib proxies for my MBeans since my setters invoke Spring AOP functionality on some base class methods. So now when I set a property from either a JMX client, or the application the client monitors, the other is notified. (Synchronization of updated values in the client is another annoying issue though).
My problem is that when I try to "drill down" into an MBean attribute, which itself is another Spring/JMX managed type, I receive a cglib2 Serialization error. My relevant classes are Serializable. A JMX client like JConsole or eclipse-jmx is of limited utility if one cannot start with a single class that it is complex composition of other JMX-ed Spring beans, and keep drilling down. The only requirements to be able to do this are supposed to be Serializability and availability of the defined classes to the JMX client, but this still results in the cglib serialization error. Does anyone know how to solve this problem?