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.
To accomplish this, you must edit the properties of the Java project to configure the BeanInfo search path that the visual editor uses. By keeping them in separate packages, you are separating design-time and run-time classes, so you can deploy them separately.
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.
Parent topic: Specifying the location of BeanInfo classes
Related concepts
BeanInfo classes and introspection
Related tasks
Keeping beans and BeanInfo classes in different projects
Keeping BeanInfo classes in a JAR file
Explicitly defining the location of BeanInfo classes
Keeping beans and BeanInfo classes in the same package