When you are creating custom or built-in controls, you can use them locally (as part of the project from which they're being used) or package them using a control project. A control project is a special kind of project that is designed to collect related controls. The result of a control project is a JAR file that can be used within other projects.
Keep in mind that for most of the controls you create, you probably won't need a control project. The primary reason for building controls within a control project is to have the resulting JAR file for portability.
To Create a New Java Control in a Java Control Project
WebLogic Workshop will create a new project folder with the name you specified. Inside the new folder will be a META-INF folder.
It is a good idea to create separate subfolders within your project for each control to contain the control's source code. Keep in mind that a folder beneath the project's top level becomes part of the control's Java package name. With this in mind, you should create a folder structure that reflects what the various controls are designed to do. Note that you cannot create the control in the root of a project — it must be in a subfolder.
When creating new controls, you may consider setting the jc-jar group-name attribute to a name corresponding to the Java Control Project. For more information, see How Do I: Specify IDE Characteristics for a Java Control?
Before you can use the new Java control anywhere in the application, you must first build and package the control project.
To Build and Package the Control Project
WebLogic Workshop compiles the control code, packages it into a JAR file with the same name as the control project's folder, and adds the control as a library available in the application. You'll find the resulting JAR file in the Libraries folder of your application.
To Import the JAR File from Another Application
To Use a New Java Control
For a control project example, see ControlProject in the SamplesApp application installed with WebLogic Workshop.