Raible's Wiki: AppFuseSupport

At line 90 changed 4 lines.

* [How to convert <bean:message> tags to JSTL's <fmt:message> tags|http://raibledesigns.com/page/rd?anchor=changing_struts_lt_bean_message]

* How to [use Velocity templates instead of JSPs|AppFuseVelocity].

* How to [deal with Dates using Struts|AppFuseStrutsDates].

* Do you have any Struts validator [examples?|http://phd.netcomp.monash.edu.au/RobertMarkBram/blog/detailPage.asp?id=46]

* I get an "xxxxx" when I run "ant new"

;:''The issue is likely because xxxxxx. See [this page|AssistanceWithAntSetup] for assistance.''

At line 95 removed 30 lines.

* Why is the JSTL keyword 'empty' not working all the time?

;:''The empty keyword (pre JSP 2.0), only worked on java.util.List, java.util.Map, on Strings and arrays. Collections like java.util.Set were not supported. If you are using pre JSP 2.0 and want to test whether a Set is empty or not use: {{{

<c:if test="${mycollection['empty']}">.

}}}

The most reliable workaround to this problem I have found, is to use this notation:

{{{

<c:forEach items="${mycollection}" var="element" varStatus="rowNum">

<c:if test="${rowNum.count==1}">

<table>

<tr> <th> Value Header </th> </tr>

</c:if>

<tr>

<th>

<c:out value="${element.value}"/>

</th>

</tr>

<c:if test="${rowNum.last}">

</table>

</c:if>

</c:forEach>

}}}

This [article|http://weblogs.java.net/blog/mister__m/archive/2003/11/crazy_jstl_when.html] explains this in more detail. If you are using tomcat 5, this supports JSP 2.0 so you will not experience

this problem.

Raible's Wiki

AppFuse

Other Applications

AppFuseSupport