Helper class to configure Tiles 2.x for the Spring Framework. See
http://tiles.apache.org
for more information about Tiles, which basically is a templating
mechanism for JSP-based web applications.
Note: Spring 3.0 requires Tiles 2.1.2 or above, with explicit support for Tiles 2.2.
Tiles 2.1's EL support will be activated by default when running on JSP 2.1 or above
and when the Tiles EL module is present in the classpath.

The TilesConfigurer simply configures a TilesContainer using a set of files
containing definitions, to be accessed by TilesView instances. This is a
Spring-based alternative (for usage in Spring configuration) to the Tiles-provided
org.apache.tiles.web.startup.TilesListener (for usage in web.xml).

setCompleteAutoload

See org.apache.tiles.extras.complete.CompleteAutoloadTilesContainerFactory
for details on the complete-autoload mode.

NOTE: Specifying the complete-autoload mode effectively disables all other bean
properties on this configurer. The entire initialization procedure is then left
to org.apache.tiles.extras.complete.CompleteAutoloadTilesInitializer.

setDefinitionsFactoryClass

Set the DefinitionsFactory implementation to use.
Default is UrlDefinitionsFactory,
operating on definition resource URLs.

Specify a custom DefinitionsFactory, e.g. a UrlDefinitionsFactory subclass,
to customize the creation of Tiles Definition objects. Note that such a
DefinitionsFactory has to be able to handle URL source objects,
unless you configure a different TilesContainerFactory.

setPreparerFactoryClass

Set the PreparerFactory implementation to use.
Default is BasicPreparerFactory, creating
shared instances for specified preparer classes.

Specify SimpleSpringPreparerFactory to autowire
ViewPreparer instances based on specified
preparer classes, applying Spring's container callbacks as well as applying
configured Spring BeanPostProcessors. If Spring's context-wide annotation-config
has been activated, annotations in ViewPreparer classes will be automatically
detected and applied.

Specify SpringBeanPreparerFactory to operate on specified preparer
names instead of classes, obtaining the corresponding Spring bean from
the DispatcherServlet's application context. The full bean creation process
will be in the control of the Spring application context in this case,
allowing for the use of scoped beans etc. Note that you need to define one
Spring bean definition per preparer name (as used in your Tiles definitions).

setServletContext

Invoked after population of normal bean properties but before an init
callback like InitializingBean's afterPropertiesSet or a
custom init-method. Invoked after ApplicationContextAware's
setApplicationContext.