You can keep your BeanInfo classes in a separate JAR file in the same project as the Java beans that they define, in a separate project, or on the file system.
To use the BeanInfo classes and browse their source code, they can be imported into a project as a ZIP or JAR file. Then the contents of the file can be expanded to their individual entries. To save space, the BeanInfo classes can be left in the JAR file, and the JAR can be imported as is.
However, in order for the BeanInfo classes in the JAR file to be used during introspection of your visual classes, you must include the JAR file in the BeanInfo Path for the project and you must name the packages in the JAR file.
To add JAR files containing BeanInfo classes to your project's BeanInfo path:
For example, the project MyProject contains the Java bean runtimeclasses.MyBean. The JAR file designtime.jar contains its BeanInfo class in the package beaninfoclasses.
You can either import the designtime.jar file into MyProject, or another project, or you can leave it on your file system. Then you add designtime.jar to the BeanInfo Path of MyProject, and name the beaninfoclasses package as the location of the BeanInfo classes.
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 beans and BeanInfo classes in different projects
Explicitly defining the location of BeanInfo classes
Keeping beans and BeanInfo classes in the same package