Controlling BeanInfo information for plug-in developers

You can exercise control over how the BeanInfo classes are associated with a class path variable by adding an entry in a plug-in manifest file.

This is only intended for advanced users who are either supplying their own Java beans or for users who want to create a new run-time environment other than JRE_LIB.

  1. Open the plugin.xml manifest file for the plug-in that contains the JAR file with the BeanInfo classes.
  2. Add a org.eclipse.jem.beaninfo.registrations extension point where you specify the variable for the location of the BeanInfo classes. For example:
    <extension point="org.eclipse.jem.beaninfo.registrations">
       <variable path="MY_JAVABEANS">
          <beaninfos>
             <beaninfo kind="plugin" path="/com.mycompany/myjavabeans.jar">
                <searchpath package="com.mycompany.beaninfopackage"/>
             </beaninfo>
          </beaninfos>
       </variable>
    </extension>

    This example shows that the class path variable MY_JAVABEANS has its BeanInfo classes contained in the JAR file myjavabeans.jar. This JAR file is part of the plug-in that the manifest is defined in, and the classes are included in the package com.mycompany.beaninfopackage. Whenever a project has the class path variable MY_JAVABEANS in its Java build path, then myjavabeans.jar will be included in the classpath of the JVM created for the introspector. Also, the package com.mycompany.beaninfopackage will be included in its search path.

(C) Copyright IBM Corporation 1999, 2004. All Rights Reserved.