Flaw in the way Model MBeans expose attributes.
I have been searching the web for a while now trying to figure out a way to expose attributes using a model mbean withOUT also exposing the getters and/or setters of these attributes as operations. First off, it seems to me to be a bug in the JMX spec that when creating a ModelMBeanInfo object (for example, using an ModelMBeanInfoSupport), that each ModelMBeanAttributeInfo must also have corresponding ModelMBeanOperations for the getters and setters. Why the need for the duplication of effort and data? Furthermore, all JMX clients I've used (namely jconsole and jmanage) then show all those redundant getters and setters in the interface, completely cluttering up the list of operations (especially if there are a lot of attributes).
Has anyone been able to work around this while still using model mbeans? I've seen a bunch of posters to other forums with this problem (for example, see http://forum.springframework.org/archive/index.php/t-25943.html on the spring JMX forums), but no good solutions.
