When you develop classes in the Visual Editor for Java, you have the option to keep your .java files and BeanInfo classes in different packages within the same project. The advantage of doing this, compared to having them in the same package, is that by decoupling design and runtime classes you can deploy them separately.
To accomplish this, you must edit the properties of the Java project to configure the BeanInfo search path that the Visual Editor uses.
For example, a project called MyProject contains the following packages:
To configure the setup just described:
When the introspector is created for the project, it includes all packages specified in the Packages list in its search path.
Related concepts
BeanInfo classes and introspection
Related tasks
Specifying the location of BeanInfo classes
Related reference
BeanInfo classes for JRE classes
BeanInfo classes for the Visual Editor for Java