> Yes, I agree with you, but so there is only a corner case where that > exception is not thrown if I call the setEnabled(false) just before the > setAction() ... so if possible I'd like a runtime exception even in this > case.
I don't think this is an exceptional condition. Calling setAction() should automatically change the button's enabled state to match the action. G