When you have a JSP file and an associated JSF Handler
part, you can begin developing the web page's behavior. This means binding,
or connecting, elements on the web page to variables and functions
in the JSF Handler.
The specific steps involved depend on the complexity of the web
page and of the related EGL parts:
- You can bind a button on the page to a function in the JSF Handler
so that when the user clicks the button, the associated function in
the JSF Handler runs. See Binding a JSF button to a function.
- You can bind input and output controls on the web page to variables
in the JSF Handler so that when the value changes on the page, the
value of the associated variable changes to match and when the value
of the variable changes in the JSF Handler, that value displayed on
the page changes. See Binding a control on a web page to a variable.
- You can bind variables in the JSF Handler to a JSF single-select
control, such as a combo box or list box. See Binding a JSF single-select control to a variable.
- You can bind an array of records to a data table on the page and
return an array of integers indicating which items the user has selected.
See Returning the indexes of selected rows in a data table.
- You can bind the inputs, outputs, and functions from a service
to controls on the page. These steps are essentially the same as binding
ordinary input, output, and command button controls to EGL variables
and functions, but EGL provides shortcuts for dealing with services
on a web page in this way. See Binding JSF controls to services.
Although EGL is not case-sensitive, JSF is. EGL names referenced
in the JSP file must have the same case as the EGL variable or function
declaration. For this reason, you should avoid changing the case of
variable or function names in a JSF Handler after binding them to
a JSF control. You can always repeat the binding process to create
a new, correct reference in the JSP file.