🚀 go-pugleaf

davout wrote:
> I've been reading up on JMX,  and I'm struggling to see how JMX can be used to report a complex state object. All of the examples and articles focus on reporting simple one element integer or string properties.
> 
> Can JMX be used to report a state that is represented by an aggregate object of multiple properties and perhaps nested sub objects?
> 
> If anybody can point me at some examples that would help.
> 
> 
> 
Actually, there is nothing in the JMX spec that dictates what your MBean 
can utilize as data types for it's attributes - just that it follow the 
naming patterns (generally: JavaBean patterns) when implementing (if a 
Standard MBean), or you have a proper MBeanInfo (if a Dynamic MBean).

For example, you can return a complex object if you choose as an 
attribute. You can pass a compex object to an operation that is defined 
for that MBean. The issue really is, what the consumer of that attribute 
data does with it, or the knowledge required between a producer of a 
complex object and the MBean that consumes it (i.e. as an argument to an 
MBean operation).

You are probably basing your question on seeing the examples that use 
the HTML Adapter as a consumer, which is tries to visually represent the 
attribute data on an HTML screen. It can "automatically" do that for the 
scalar data types, but obviously has no clue how to render a Foo object.
-- 
Tad Frysinger [TeamB]