<logic:iterate id="employee" name="employees">
<tr align="left">
<td>
<bean:write name="employee" property="username" />
</td>
<td>
<bean:write name="employee" property="name" />
</td>
<td>
<bean:write name="employee" property="phone" />
</td>
</tr>
</logic:iterate>
<logic:present parameter="username">
Welcome <%= username %>.
</logic:present >
In this example, we test for the existence of the request parameter username. If the username parameter is part
of the request, then the tag’s body will be evaluated.
<logic:notPresent name="username" scope="session">
There is no username attribute in the session.
</logic:notPresent >
In this example, we test for the existence of the session attribute username. If the username parameter is not
found in the HttpSession, then the tag’s body will be evaluated.
<logic:forward name="login" />
In this example, we forward the current request to the global forward login. This resource must be defined in
the <global−forwards /> section of the struts−config.xml file.
<global−forwards>
<forward name="login" path="/login.jsp"/>
</global−forwards>
<logic:redirect name="login"
paramId="companyId" paramName="company" />
In this example, we perform a redirect to the global forward login. This resource must be defined in the
<global−forwards /> section of the struts−config.xml file. The <logic:redirect /> tag differs from the
<logic:forward /> tag in that the <logic:redirect /> tag allows you to dynamically augment the request with
parameters.
<logic:empty name="user">
<forward name="login" />
</logic:empty>
In this example, we test the scripting variable user. If this variable is null or an empty string, then the body
will be evaluated, which will result in the user being forwarded to the global forward login.