FULL PRODUCT VERSION :
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)


ADDITIONAL OS VERSION INFORMATION :
 customer  Windows XP [Version 5.1.2600]

A DESCRIPTION OF THE PROBLEM :
When trying to edit attributes in MBeans with multiple writable attributes, I
find it very easy to get the Attributes table into a state wherein I cannot get
the UI to enter edit mode for another writable attribute.  I can "reset" the UI,
by selecting another MBean and then selecting the desired MBean and things are fine again -- for a while.

This may also be reproducible for MBeans with only a single writable attribute
-- I'm not 100% certain.  It is reproducible with both Java 6 Update 7 and Java
6 Update 10 (build 27).  It is also reproducible in VisualVM's MBeans plug-in.  See VisualVM issue #167.

This is quite annoying and hard to explain to users.  For all I know this could
be a Swing bug -- in which case it needs to be fixed yesterday.  This sort of
edit glitch erodes trust and user  customer  will for the entirety of the application
or UI framework.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Click on various writable attributes to edit.  Doing so a few times on different attributes will quickly get the UI into a state wherein no cell editor is produced for any clicks!

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Single clicking on writable attributes should always produce an appropriate cell editor.
ACTUAL -
No cell editor is produced.

REPRODUCIBILITY :
This bug can be reproduced often.

CUSTOMER SUBMITTED WORKAROUND :
The only workaround appears to be to select another MBean in the MBean tree and then select the desired MBean again.
Posted Date : 2008-08-04 17:28:31.0

The problem appears if you move the mouse out of the edited field without validating the edited field first. So the work around is simply to validate the field before moving the mouse out of it.

If you are in a situation where the UI is blocked, then moving the mouse out of the window, clicking it out of the window, and moving the mouse back to the editor should unblock the UI.

Not ideal - but at least it can be a temporary workaround.
 
*** (#1 of 1): [ UNSAVED ]   xxxxx@xxxxx  

The problem appears if you move the mouse out of the edited field without validating the edited field first.
Posted Date : 2008-08-04 17:40:42.0