All AWT components qualify as java beans by virtue of the fact that they adhere to JavaBeans design patterns for method signatures. The term design pattern does not equate to the popular object-oriented term but instead simply refers to a method naming convention. By adhering to JavaBeans design patterns for property accessors and event handling methods, any AWT component can be manipulated in a JavaBeans builder tool.
 See Gamma, Helm, Johnson, Vlissides. Design Patterns, Addison-Wesley, 1994.
In addition to using JavaBeans design patterns for method signatures, AWT components also come with (the ability to implement) bound properties.
Bound properties are properties that result in a notification ...