###@###.###

A pretty straightforward AWT implementation problem:

Calling certain native methods on AWT components that
have been disposed cause segmentation faults. For
example, the code:
{
Label err = new Label("",null,window,font);
err.dispose();
err.setText("This will break");
}
will cause the fault. Since there is currently no method
of determining whether a component is ``valid'', it would
be nice if this would at least just throw an exception,
rather than killing java...