When Application Developer starts, it reads every plug-in.xml file contained in folders within the plugins directory. The extension points in the plug-in.xml file will define the rules for the container Visual_Beans. After the plug-in has been installed, toolkit beans are available in the palette in the same way as Swing or AWT components.
When you open the Visual Editor for Java, you will see that the categories defined in the XMI file have been added at the top of the palette. You can select the JavaBeans(TM) and drop them onto the canvas without having to use the Choose Bean dialog. The following image shows what you will see in the palette:
To open the Visual Editor for Java, you must first create a visual class (or load one of the sample applications) and then open it with the Visual Editor.
If the plug-in does not appear in the list of containers for the project, there may be errors in the plugin.xml file. WebSphere Studio writes any errors in the .log file in the .metadata directory. For example, if you forgot to include a version attribute in the plugin tag, an error will be written to the log file.