The new monitor functionnality dealing with complex attributes and introduced
in the mustang release is described in the monitor package javadoc.
Some parts of this javadoc should be clearer, especially :
- the part dealing with the rules where we start dealing with an example
  (HeapMemory.used), than switch to a more generic context and declare A.e,
  than v, than x...
  It seems (to be confirmed) that the first letter of the second attribute name
  is not case sensitive, so we could deal with a generic example using attribute name
  "A.B" with returned values "a" and "b" respectively.
  Than just quote the heap memory example.
- the part dealing with observed attribute name "A.B" where A.B is the name
  of an MBean attribute returned by getMBeanInfo.
  What should be clarified is the case where "A" and "A.B" are returned by
  getMBeanInfo and we observe the "A.B.C". In this case, it is implicit the rules
  described above are applied but perhaps this particular case (tested in the JCK)
  should be explicit as well
###@###.### 2005-04-27 15:00:35 GMT