First page Back Continue Last page Graphics


Notes:

Using ADF Faces Input Components (continued)

Selecting one or more values from lists: The selection features you can use include:

Select a value by using a check box (selectBooleanCheckbox ) or selecting a option button (selectOneRadio or selectBooleanRadio).

Select a single value from a list or menu (inputListOfValues or selectOneChoice).

Select from a list that includes a search and select dialog box (inputComboboxListOfValues).

Select multiple values from a list or menu (selectManyCheckbox, selectManyChoice, or selectManyListbox).

Select multiple values from a list of values by shuttling values between two lists, adding and removing values from the target list (selectManyShuttle or selectOrderShuttle).

The ADF Faces Rich Text Editor component provides users with the ability to edit rich text. Text formatting features supported include:

Text and background colors

Font name, size, and weight

Text decoration such as underline and strikethrough

Ordered and unordered lists

Text justification (left, right, center, or full)

Undo and redo

Link and unlink

Clear styling

Undo and redo

Subscript and superscript

You can provide features for users to upload files (inputFile).

Input components are usually contained within a form or subform component. A form is a component that serves as a container for other components. When you add input components, you need to embed those components within a form structure. For example, if you add an af:inputNumberSlider to a page, it must be enclosed or be a child component within an af:form.

Within a form you can also add an af:subform, which represents a portion of the page that can be independently submitted. The contents of a subform are validated (or otherwise processed) only if a component inside the subform is responsible for submitting the page. This allows for comparatively fine-grained control of which components will be validated and pushed into the model without the compromises of using entirely separate form elements.

Oracle recommends the use of a single <af:form> per page, along with using <af:subform> instead of multiple forms. Multiple forms require multiple copies of page state, and user edits in forms that aren’t submitted are always lost. When a page using subforms is submitted, page state is only written once, and all user edits are preserved.

You can include a button to reset the content of all input items to their default values (af:esetButton).

To see descriptions of how to use these input components, you can hold the cursor over the name of the component in the Component Palette.