| |||||||
FRAMES NO FRAMES |
Define a faces flow.
VDL usage
Several conventions apply when using this element in a VDL view, but in all cases, the presence of this element in a VDL view indicates that this view must be considered as a ViewNode
of the flow. There are two varieties of usage of this element within VDL views: the "flow defining view" and the "member view". In any given VDL defined view, there must be exactly one flow defining view and zero or more member views.
Identifying the flow defining view
The flow defining view must be the first view in a flow that is encountered during a user's traversal of the application.
If this VDL view resides in a directory whose name is equal to the filename of the VDL view, the directory name is taken to be the id of the flow, and the value of the id attribute of the <faces-flow-definition>
, if any, is ignored. If there is no <start-node>
defined, it assumed to be the VDL view in which this element appears.
If this VDL view does not reside in a directory, or resides in a directory whose name is not equal to the filename of the VDL view, the id and <start-node>
must be explicitly specified.
faces-config usage
The entire flow is defined as child elements, or references to other elements of this element.
Tag Information | |
Tag Class | None |
TagExtraInfo Class | None |
Body Content | empty |
Display Name | None |
Attributes | ||||
Name | Required | Request-time | Type | Description |
id | false | false | javax.el.ValueExpression
(must evaluate to java.lang.String )
| No Description |
Variables | No Variables Defined. |
| |||||||
FRAMES NO FRAMES |