When you create a Forms application, you can extend and customize its functionality.
This can be done in two ways:
The JavaBeans and customized components supported by WebForms are referred to as Pluggable Java Components (PJCs).
The Forms supplies you with interface mechanisms that allow you to easily add JavaBeans and customized interface components to your application.
Your JavaBeans and customized components make use of a special Forms-defined interface, called the IView interface. This Java interface is provided for you.
Your JavaBeans also make use of a special Forms-provided Java class, called
the VBean
class. By wrapping your JavaBean in a container that
extends this class, your JavaBean can easily communicate with your form at runtime.
The JavaBean can be started from the form, and values can be passed back and
forth.
In addition to the IView
interface and VBean
class,
WebForms also provides you with certain form properties, Built-ins, triggers,
and system variables for communicating with your pluggable components.
For the end user at runtime, the JavaBean is represented by an interface item on the screen. Clicking on the item initiates the execution of the JavaBean. Other controls and data items may also be associated with the bean, to allow runtime interaction or display of changed values or results.
During its initiation process at the beginning of runtime, WebForms sets up communication mechanisms with the JavaBean. WebForms accesses your container class and instantiates the container and its bean. This initiation process registers a listener relationship, so that properties can be shared and events communicated during runtime.
Elements in the WebForms product affected by this new Pluggable Java Components feature include:
How to Add JavaBeans by Writing Your Own Java Code