| NetUI Tag Library Documentation | ||||||
| FRAMES NO FRAMES |
A, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowA, C, E, F, G,
H, V, left arrow, and right arrowaction
attribute of the parent <netui:form> tag.
<td cell="alternatingCellClass">isAlwaysReport is set to true, then the errors will be displayed in Production mode
as well as in Development mode. Otherwise, the errors will be displayed only in Development mode.Generates an anchor that can link to another document or invoke an action method in the Controller file.
Data grid cell used to render an HTML anchor.
Adds an attribute to the parent tag rendered in the browser.
scope attribute.request or session) under which the associated Form Bean
used to populate the form input fields is stored.
Using the name, type and scope attributes defines
the Form Bean used.name and scope attributes are set.
The Form Bean is then used to populate the form input fields.Renders an HTML <body> tag with the attributes specified.
- com/foobar/resources/WebAppProperties
- com.foobar.resources.WebAppProperties
These are treated as equivalent values. The java.util.ResourceBundle class
will handle appending the .properties file type and locale information
as necessary. See java.util.ResourceBundle.getBundlegetBundle(String, Locale, ClassLoader)
for the .properties file naming conventions. These files must be available in
classpath for the webapp in order to be successfully located.
The Caption tag is used to render an HTML <caption> inside of a data grid.
<td class="cellClass">
Generates a single HTML checkbox.
columns attribute is specified but
the rows attribute is not, the rows attribute will be inferred
using the size of the data set.The configurePager tag is used to parameterize the data used to render a data grid's pager.
This tag is the containing tag for all tags and markup used to render a data grid.
Set the org.apache.beehive.netui.databinding.datagrid.api.DataGridConfig instance that this tag will use to create state containers and other data grid objects used during rendering. Custom implementations of this class can be provided that will override the defaults set in the org.apache.beehive.netui.databinding.datagrid.runtime.config.DefaultDataGridConfig.
dataInput attribute) and return the value to a new destination (whatever is
referenced by the dataSource attribute).
This attribute may take a String literal or a data binding expression.The dataSource attribute determines both
(1) the source of populating data for the tag and
(2) the object to which the tag submits data.
For example, assume that the Controller file (= JPF file) contains a Form Bean with the property foo. Then the following <netui:textBox> tag will (1) draw populating data from the Form Bean's foo property and (2) submit user defined data to the same property.
<netui:textBox dataSource="actionForm.foo" />
When the tag is used to submit data, the data binding expression must refer to a Form Bean property. In cases where the tag is not used to submit data, but is used for displaying data only, the data binding expression need not refer to a Form Bean property. For example, assume that myIterativeData is a member variable on the Controller file ( = JPF file). The following <netui-data:repeater> tag draws its data from myIterativeData.
<netui-data:cellRepeater dataSource="pageFlow.myIterativeData">
Set the data source that references a data set to be rendered by the data grid. The data source should be a NetUI EL expression and generally looks like a JSP EL expression without the '${' and '}' characters. For example, to reference an array of Employee objects exposed via a NetUI page input, the expression might look like:
<netui-data:dataGrid dataSource="pageInput.employeeArray" name="employeeGrid">
This expression will be evaluated the data grid in order to obtain a reference to the data set.
The dataSource attribute determines both
(1) the source of populating data for the tag and
(2) the object to which the tag submits data.
For example, assume that the Controller file (= JPF file) contains a Form Bean with the property foo. Then the following <netui:textBox> tag will (1) draw populating data from the Form Bean's foo property and (2) submit user defined data to the same property.
<netui:textBox dataSource="actionForm.foo" />
The dataSource attribute takes either a data binding expression or
the name of a Form Bean property. In the
above example, <netui:textBox dataSource="foo" />
would have the exactly same behavior.
When the tag is used to submit data, the data binding expression must refer to a Form Bean property. In cases where the tag is not used to submit data, but is used for displaying data only, the data binding expression need not refer to a Form Bean property. For example, assume that myIterativeData is a member variable on the Controller file ( = JPF file). The following <netui-data:repeater> tag draws its data from myIterativeData.
<netui-data:repeater dataSource="pageFlow.myIterativeData">
The dataSource attribute determines both
(1) the source of populating data for the tag and
(2) the object to which the tag submits data.
For example, assume that the Controller file (= JPF file) contains a Form Bean with the property foo. Then the following <netui:textBox> tag will (1) draw populating data from the Form Bean's foo property and (2) submit user defined data to the same property.
<netui:textBox dataSource="actionForm.foo" />
The dataSource attribute takes either a data binding expression or
the name of a Form Bean property. In the
above example, <netui:textBox dataSource="foo" />
would have the exactly same behavior.
When the tag is used to submit data, the data binding expression must refer to a Form Bean property. In cases where the tag is not used to submit data, but is used for displaying data only, the data binding expression need not refer to a Form Bean property. For example, assume that myIterativeData is a member variable on the Controller file ( = JPF file). The following <netui-data:repeater> tag draws its data from myIterativeData.
<netui-data:repeater dataSource="pageFlow.myIterativeData">
The dataSource attribute determines both
(1) the source of populating data for the tag and
(2) the object to which the tag submits data.
For example, assume that the Controller file (= JPF file) contains a Form Bean with the property foo. Then the following <netui:textBox> tag will (1) draw populating data from the Form Bean's foo property and (2) submit user defined data to the same property.
<netui:textBox dataSource="actionForm.foo" />
The dataSource attribute takes either a data binding expression or
the name of a Form Bean property. In the
above example, <netui:textBox dataSource="foo" />
would have the exactly same behavior.
When the tag is used to submit data, the data binding expression must refer to a Form Bean property. In cases where the tag is not used to submit data, but is used for displaying data only, the data binding expression need not refer to a Form Bean property. For example, assume that myIterativeData is a member variable on the Controller file ( = JPF file). The following <netui-data:repeater> tag draws its data from myIterativeData.
<netui-data:repeater dataSource="pageFlow.myIterativeData">