At we were redesigning our control and view layers. We had already decided on Spring-Web as a
framework for the control layer due to its flexibility and a design
providing a simpler migration path. For the front end we were a
little unclear. One of the alternatives we looked at was Apache Tiles. It follows the Composite Pattern... This meant it provided by default what we considered a superior design... It already had
integration with Spring, and the way it worked ... gave us a
clear MVC separation and an encapsulation ensuring single thread
safety within the view domain.

Yet the most valuable benefits Tiles had to offer wasn’t realised until we started experimenting a little more…

The full story of and Tiles-2 can be read here.