### Create new RichFaces Documentation Jira issue

Summary
255 characters left
Description
Environment
This will launch the RichFaces Jira page - to complete your feedback please login if needed, and submit the Jira.

JBoss.org Community Documentation

- Prev
- Next

## 6.41. < rich:dataDefinitionList >

### 6.41.1. Description

The component for definition lists rendering that allows choosing data from a model and obtains built-in support of Ajax updates.

Figure 6.79. <rich:dataDefinitionList> component

### 6.41.2. Key Features

- Completely skinned table rows and child elements

- Possibility to update a limited set of rows with AJAX

- Possibility to receive values dynamically from a model

Table 6.157. rich : dataDefinitionList attributes

Attribute Name | Description
--- | ---
ajaxKeys | This attribute defines row keys that are updated after an AJAX request
binding | The attribute takes a value-binding expression for a component property of a backing bean
columnClasses | Comma-delimited list of CSS style classes that are be applied to the columns of this table. A space separated list of classes may also be specified for any individual column. If the number of elements in this list is less than the number of columns specified in the "columns" attribute, no "class" attribute is output for each column greater than the number of elements in the list. If the number of elements in the list is greater than the number of columns specified in the "columns" attribute, the elements at the position in the list after the value of the "columns" attribute are ignored
componentState | It defines EL-binding for a component state for saving or redefinition
dir | Direction indication for text that does not inherit directionality. Valid values are "LTR" (left-to-right) and "RTL" (right-to-left)
first | A zero-relative row number of the first row to display
id | Every component may have a unique id that is automatically created if omitted
lang | Code describing the language used in the generated markup for this component
rendered | If "false", this component is not rendered
rowClasses | A comma-delimited list of CSS style classes that is applied to popup table rows. A space separated list of classes may also be specified for any individual row. The styles are applied, in turn, to each row in the table. For example, if the list has two elements, the first style class in the list is applied to the first row, the second to the second row, the first to the third row, the second to the fourth row, etc. In other words, we keep iterating through the list until we reach the end, and then we start at the beginning again
rowKey | RowKey is a representation of an identifier for a specific data row
rowKeyConverter | Converter for a RowKey object.
rowKeyVar | The attribute provides access to a row key in a Request scope
rows | A number of rows to display, or zero for all remaining rows in the table
style | CSS style(s) is/are to be applied when this component is rendered
styleClass | Corresponds to the HTML class attribute
title | Advisory title information about markup elements generated for this component
value | The current value for this component
var | A request-scope attribute via which the data object for the current row will be used when iterating

Table 6.158. Component identification parameters

Name | Value
--- | ---
component-type | org.richfaces.DataDefinitionList
component-class | org.richfaces.component.html.HtmlDataDefinitionList
component-family | org.richfaces.DataDefinitionList
renderer-type | org.richfaces.DataDefinitionListRenderer
tag-class | org.richfaces.taglib.DataDefinitionListTag

### 6.41.3. Creating the Component with a Page Tag

To create the simplest variant of dataDefinitionList on a page, use the following syntax:

Example:

    ...

        <rich:dataDefinitionList value="#{bean.capitals}" var="caps">

            <f:facet name="term">Cars</f:facet>

            <h:outputText value="#{car.model}"/>

        </rich:dataDefinitionList>

    ...

### 6.41.4. Creating the Component Dynamically Using Java

Example:

    import org.richfaces.component.html.HtmlDataDefinitionList;

    ...

    HtmlDataDefinitionList myList = new HtmlDataDefinitionList();

    ...

### 6.41.5. Details of Usage

The <rich:dataDefinitionList> component allows to generate an definition list from a model.

The component has the "term" facet, which corresponds to the "type" parameter for the <DT> HTML element.

Here is an example:

    ...

        <h:form>

            <rich:dataDefinitionList var="car" value="#{dataTableScrollerBean.allCars}" rows="5" first="4" title="Cars">

                <f:facet name="term">

                    <h:outputText value="#{car.make} #{car.model}"></h:outputText>

                </f:facet>

                <h:outputText value="Price:" styleClass="label"></h:outputText>

                <h:outputText value="#{car.price}" /><br/>

                <h:outputText value="Mileage:" styleClass="label"></h:outputText>

                <h:outputText value="#{car.mileage}" /><br/>

            </rich:dataDefinitionList>

        </h:form>

    ...

This is a result:

Figure 6.80. <rich:dataDefinitionList> component with "term" facet

In the example the "rows" attribute limits number of output elements of the list.

"first" attribute defines first element for output. "title" are used for popup title.

The component was created basing on the <a4j:repeat> component and as a result it could be partially updated with Ajax. The "ajaxKeys" attribute allows to define row keys that are updated after an Ajax request, you need to pass an array with key (lines) of the list that you want to be updated after the Ajax request is executed.

Here is an example:

Example:

    ...

        <rich:dataDefinitionList value="#{dataTableScrollerBean.allCars}" var="car" ajaxKeys="#{listBean.list}"

                            binding="#{listBean.dataList}" id="list">

            ...

        </rich:dataDefinitionList>

    ...

        <a4j:commandButton action="#{listBean.action}" reRender="list" value="Submit"/>

    ...

In the example "reRender" attribute contains value of "id" attribute for <rich:dataDefinitionList> component. As a result the component is updated after an Ajax request.

### 6.41.6. Look-and-Feel Customization

For skinnability implementation, the components use a style class redefinition method. Default style classes are mapped on skin parameters.

There are two ways to redefine the appearance of all <rich:dataDefinitionList> components at once:

- Redefine the corresponding skin parameters

- Add to your style sheets style classes used by a <rich:dataDefinitionList> component

### 6.41.7. Definition of Custom Style Classes

On the screenshot there are classes names that define styles for component elements.

Figure 6.81. Style classes

Table 6.159. Classes names that define a list appearance

Class name | Description
--- | ---
rich-deflist | Defines styles for an html <dl> element
rich-definition | Defines styles for an html <dd> element
rich-definition-term | Defines styles for an html <dt> element

In order to redefine styles for all <rich:dataDefinitionList> components on a page using CSS, it's enough to create classes with the same names (possible classes could be found in the tables above) and define necessary properties in them.

Example:

    ...

    .rich-definition-term{

     font-weight:bold;

    }

    ...

This is a result:

Figure 6.82. Redefinition styles with predefined classes

In the example a term font weight was changed.

Also it's possible to change styles of particular <rich:dataDefinitionList> component. In this case you should create own style classes and use them in corresponding <rich:dataDefinitionList> styleClass attributes. An example is placed below:

Example:

    ...

    .myClass{

      font-style: italic;

    }

    ...

Example:

    <rich:dataDefinitionList ... rowClasses="myClass"/>

This is a result:

Figure 6.83. Redefinition styles with own classes and styleClass attributes

As it could be seen on the picture above, the font style for rows was changed.

### 6.41.8. Relevant Resources Links

On the component LiveDemo page you can see the example of <rich:dataDefinitionList> usage and sources for the given example.

- Prev6.40. < rich:dataOrderedList >
- Top of page
- Front page
- Next6.42. < rich:dataTable >