AWT Containers and the BeanContextProxy Interface

Sometimes, it is desirable for an AWT Container to act as a BeanContext. However, AWT Containers cannot implement the BeanContext interface directly, because of a method name collision between Component and Collection. If some AWT Component needs to act as a BeanContext, it must internally create a BeanContext instance and delegate work to it. Third parties, such as visual builder tools, can discover this BeanContext instance if the Component implements the BeanContextProxy interface.

The BeanContextProxy Interface