RE: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

  • From: "KARR, DAVID" <dk068x@...>
  • To: "users@..." <users@...>
  • Subject: RE: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?
  • Date: Fri, 27 Dec 2013 19:27:17 +0000
  • Accept-language: en-US

> -----Original Message-----
> From: Tomas Hurka [mailto:tomas.hurka@...]
> Sent: Friday, December 27, 2013 12:03 AM
> To: users@...
> Subject: Re: Where in the JMX specification does it describe how properties
> in the ObjectName results in hierarchical folders?
> 
> Hi David,
> 
> On 21 Dec 2013, at 18:48, KARR, DAVID wrote:
> >>>
> >>> I don't understand.  How does this answer my question?  What is an
> "ordered
> >> key property list" and what is the relation to properties like "00" and
> "01"?
> >> I guess this is constructed from ObjectName. ObjectName consist of 
> >> domain,
> >> (:) and key property list. So in your case:
> >> ":00=org,01=apache,02=stuff,03=gork,name=ComponentName"
> >> domain is empty and key property list is
> >> 00=org
> >> 01=apache
> >> 02=stuff
> >> 03=gork
> >> name=ComponentName
> >>
> >> Since there is no "type" or "j2eeType" key, the order of folders in
> VisualVM
> >> and JConsole is
> >> org
> >> |
> >> +-> apache
> >>        |
> >>        +-> stuff
> >>              |
> >>              +-> gork
> >>                   |
> >>                   +-> ComponentName
> >>
> >> Is it clear now?
> >
> > No.  What algorithm is translating those "00", "01", et cetera values to
> produce that tree?  What is the significance of the first digit?  The second
> digit?  What if a value had a third digit?
> Keys in the "ordered property list" ("00", "01", etc.) has no meaning. Only
> order is significant.

Ok, so taking all of this into account, would you say this is a reasonable 
statement of the algorithm used to build the tree?  It doesn't matter if the 
code does exactly these steps, just whether it would end up with the same 
result in the end.
--------------
Get ObjectName properties into a list.
Sort list in alphabetical order of the property keys.
If a property key of "j2eeType" is in the list, move it to the first entry, 
pushing others down.
If a property key of "type" is in the list, move it to the first entry, 
pushing others down.
Using resulting sorted list, create a tree node for each property, with the 
property value being the node name, and the last property in the list being 
the leaf node for the actual mbean.
--------------


Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

KARR, DAVID 12/19/2013

Re: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

Jess Holle 12/19/2013

RE: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

KARR, DAVID 12/19/2013

Re: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

Jess Holle 12/19/2013

Re: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

Tomas Hurka 12/20/2013

RE: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

KARR, DAVID 12/21/2013

Re: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

Tomas Hurka 12/21/2013

RE: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

KARR, DAVID 12/21/2013

Re: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

Tomas Hurka 12/27/2013

RE: Where in the JMX specification does it describe how properties in the ObjectName results in hierarchical folders?

KARR, DAVID 12/27/2013
Terms of Use; Privacy Policy; Copyright ©2013-2014 (revision 20131025.e7cbc9d)
 
 
Close
loading
Please Confirm
Close