🚀 go-pugleaf

At a guess (and I know nothing at all about JMX), the objects you can pass
back and forth should all implement the java.io.Serializable interface.  If
you have a serializable object, you should be able to use it in JMX.

-- 
Check out our latest white papers at
http://www.datadevelopment.com/papers/index.html

BladeNET Scores With Borland Enterprise Tools
Team Development with JBuilder and Borland Enterprise Server

Dolphin Data Development Ltd.
http://www.datadevelopment.com/

"davout" <daZZZYYYXXXvout@dsl.pipex.com> wrote in message
news:40a39286$1@newsgroups.borland.com...
>
> 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.
>
>
>

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]

davout wrote:
>>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.
>>-- 
> 
> 
> You've hit the problem on the head.
> 
> Is it possible to extend the HTML adapter to manage the display of complex
> data objects?
> 
> My situation centres around a complex tree like structure of data that
> represents the state of a data manipulation service. The tree is irregular
> in shape, can have any a variable number of hierarchy levels and child
> nodes.
> 
> 
> 
> 
The source for the HTML adapter doesn't get shipped, so no. You might 
try downloading JBoss - they also have a visual tool for viewing JMX 
objects. They obviously have no clue about your Foo object either, but 
you could use this as a starting point and build your own.

-- 
Tad Frysinger [TeamB]