Java controls are a key part of the programming model for those writing web applications with WebLogic Workshop. Controls can be used to capture the bulk of an application's business logic, encapsulate access to resources with a simplified interface for developers, and so on.
This guide is intended for those building more sophisticated packaged controls. WebLogic Workshop provides rich run-time support and an API for building controls that support design-time features through IDE extensions, customization through JCX files, and asynchronous operation.
The content in this guide assumes familiarity with the following control-related terms.
Controls installed with the IDE are known as platform controls; additional controls built by application developers, independent software vendors, and others are known as custom controls.
Simple custom controls may be written as local controls. A control is local when it is used as source in the same project as its container. This is a simple way for application developers to partition business logic. However, local controls provide limited access to the features available to controls.
A regular control does not generate a JCX file; an extensible control does. Because a JCX file is generated, an extensible control supports design-time customization. For example, an extensible control can support the user's changing the control's interface by adding, removing, and editing methods and callbacks. It can also be customized in a way that is not editable by the user; an example is the EJB control, whose interface is defined by the EJB it will be accessing.
For more information on creating extensible controls, see Creating Extensible Controls.
A control deliverable is a JAR or ZIP file that contains all the files -- implementation, GIFs, annotation XML files, and so on -- required to use the control. A control stub is a JAR file that contains merely the information needed to make the control's availability visible to users, along with a URL from which the IDE may download the control the first time the user chooses to add it to an application. Together, these are known as available controls. This is a just-in-time approach to control delivery and use. For more information, see Packaging Controls for Installation.
The material in this guide is intended for those building packaged custom controls that use the advanced features available for Java controls. This guide is intended to complement the material contained in the core WebLogic Workshop documentation (under "Working with Java Controls"). If you're looking for information about Java control concepts that's not covered here, it's likely you'll find it there.
In building an advanced Java control, the tasks you'll perform are likely to include:
None.