>> My question is about the filter field in the JMX tree. >> What does this field actually filter on ? i.e. if I enter "name" it >> shows me alot of nodes which does not seem to have "name" in them. The filter works on the MBean's ObjectName. Typing "name" will match any MBeans which has a property with a "name" key (and a lot of MBeans will match!). The MBean Explorer display only the values of the ObjectName properties (as nodes of its tree). To make it consistent with the UI, a refinement could be to filter only on the ObjectName properties values (and not their keys).

>> And is it intentional the search is casesensitive ? (I for one cannot >> figure out the random camel casing in JMX names ;) yes, the filter is case sensitive.

>> In the tree is double click not supposed to do something when I click >> on operations ? i.e. open the editor and have that property/method >> selected ready for execution ? Normally, double-click on a operation in the MBean explorer must open the corresponding MBean editor and select the given operation. This issues appeared when the implementation switched to using the Common Navigator.