Configuration Reference - Stripes...and Java Web Development is Fun Again - page 362

have commons-fileupload.jar and commons-io.jar in the class path, or it's
CosMultipartWrapper if you have cos.jar in the class path. If neither imple-
mentation can be loaded, a debugging message is logged. No exception
is thrown because not all web applications need to support file uploads.
To use a different implementation, use the following:
<init-param>
<param-name> MultipartWrapper.Class </param-name>
<param-value> stripesbook.nonext.MyMultipartWrapper </param-value>
</init-param>
PopulationStrategy.Class
This is the implementation of the PopulationStrategy interface to populate
the values of form input tags. The default is DefaultPopulationStrategy . As
we saw on page 189 , the BeanFirstPopulationStrategy is a useful alterna-
tive:
<init-param>
<param-name> PopulationStrategy.Class </param-name>
<param-value>
net.sourceforge.stripes.tag.BeanFirstPopulationStrategy
</param-value>
</init-param>
TagErrorRendererFactory.Class
This is the implementation of the TagErrorRendererFactory interface,
which returns objects that implement TagErrorRenderer . The default is
DefaultTagErrorRendererFactory . Here's an example:
<init-param>
<param-name> TagErrorRendererFactory.Class </param-name>
<param-value>
stripesbook.nonext.MyTagErrorRendererFactory
</param-value>
</init-param>
TagErrorRenderer.Class
This is the implementation of the TagErrorRenderer interface, which for-
mats form input fields when they are in error. This parameter is loaded
by DefaultTagErrorRendererFactory . The default is DefaultTagErrorRenderer .
Here's an example:
<init-param>
<param-name> TagErrorRenderer.Class </param-name>
<param-value> stripesbook.nonext.MyTagErrorRenderer </param-value>
</init-param>