Much of what is discussed in this section are repetition of the discussion in the behavior-define and behavior logic descriptors.

Just like the logic behavior could use to determine visibility of segments, the repeat behavior could be used to determine the rendering of a segment zero, once or many times.

The repeat behavior, just like the behavior-define, could expose objects to the elements within the segments that it encloses.

<c:forEach items=="#{books}"
	var="i" begin="1" end="20" step="1" varStatus ="status"<

SEAM Enhancements

The c:forEach tag that requires caution when used in JSF with JSP, does not carry such cautionary note when used with Seam and Facelets. The underlying Facelet understand component assembly, whereas JSP does not.

Nonetheles, the ui:repeat component is preferred for usage almost always instead of the c:forEach to iterate over content with JSF.

One advantage this component brings, is the repeat region that does not have in-build template. Other repeat components, like dataTable have in-built table structure, whereas this component allows more flexibilities. Example is shown below.

...
<dl>
    <ui:repeat value="#{faculty.departments}" var="dept">
    <dt>#{dept.name}</dt>
	    <ui:repeat value="#{dept.students}" var="stud">
		<dd>#{ stud.lastName}, #{ stud.firstName}</dd>
	    </ui:repeat>
    </ui:repeat>
</dl>
...