[ BUILD # : 20070928 ]
[ JDK VERSION : 1.6.0_02 ]

The form editor can only see beans in the form for which it manages
the instance. If the user were to add instances of beans to the class
from the Java editor then the form editor should use those as well.
This would make it easier to use beans when the user added the
instance in the Java editor versus the form editor. These would not
end up showing under the hierarchy like the form editor added
instances of visual components, but would instead show up in the
"Other Components" of the inspector/hierarchy. This would then allow
them to be used in other places such as bean binding and to set the
properties of them in initComponents. 

One problem might be the user is setting properties in other
locations, but should not really matter as the user can do this for
form editor managed instances. If the instance is removed from the
Java file then I believe there are events which can be listened to in
which the form editor could remove the logic from initComponents and
events for the instance, or those methods could be left alone...which
ever we do now when we delete an instance from the UI editor.