The ControlDevKit application that accompanies these help topics contains a number of projects that demonstrate some of the key features and functionality for creating to-be-redistributed controls. A description of these projects is given below.
The samples in this project illustrate individual advanced features of Java controls. In particular, they demonstrate how to implement IDE extensions that provide customizable behavior in WebLogic Workshop. Other samples illustrate advanced event and callback related features. You can use the web services in the ControlTest project to try out these controls (see below).
The following list describes features illustrated by the samples:
EventRaiser — Using the JbcContext.raiseEvent method to forward callbacks to the control's client.
EventScheduler — Using the JbcContext.scheduleEvent method to specify that a control callback should be invoked at a particular time.
LifeCycle — Callback handlers a control can implement to handle the events in its life.
ServerCheck (and accompanying files) — Implementing a custom insert dialog for a control. The control wizard in this example extends ControlWizardSimple, which provides much of the user interface for inserting the control.
CustomWiz (and accompanying files) — Implementing a fully-custom insert dialog for a control. The wizard in this example extends ControlWizard, which allows you to implement an insert dialog that does not inherit user interface components in a dialog provided by WebLogic Workshop.
CustomerData (and accompanying files) — Implementing support for an attribute editing and validation dialog.
Contains test web services for the controls in the other two projects.
Contains a more complete example of a functional control. This control defines new JDBC data sources and their associated connection pools, and runs script files against the newly created or existing data sources. The control generates a JCX file at insert time and also supports a callback interface. This sample also illustrates how you can include documentation and sample code in such a way that it will be automatically integrated with the user's installation when they install the control from a control deliverable. For more information on packaging documentation and samples for automatic installation, see Packaging Controls for Installation.
None.