When you develop classes in the visual editor for Java, you have the option to keep your .java files and BeanInfo classes in different projects. This enables you to easily develop and deploy the classes separately.
For example, MyProject contains the class runtimeclasses.MyJavaBean. A second project, MyBeanInfoProject, contains the package beaninfoclasses.MyJavaBeanBeanInfo.
Because a BeanInfo class needs to know the class it represents, MyBeanInfoProject must include MyProject in its Java build path. Note that the reverse is not true - MyProject should not include MyBeanInfoProject in its Java build path, because this creates a circular reference.
To configure your workbench setup so that BeanInfo classes are stored in a different project from your .java files:
The steps to specify the location of a project's BeanInfo classes when they are in another project are now complete.
Notes:
Parent topic: Specifying the location of BeanInfo classes
Related concepts
BeanInfo classes and introspection
Related tasks
Keeping beans and BeanInfo classes in different packages in the same project
Keeping BeanInfo classes in a JAR file
Explicitly defining the location of BeanInfo classes
Keeping beans and BeanInfo classes in the same package