Page History

...

The things to do are:

• Remove deprecations.
• Remove parameter-based configuration, and move toward pure Java configuration.  The parameter-based configuration is hard to maintain and difficult to test.
• Use a chain-of-responbility pattern, since Tiles seems to work in several processing steps.
• Extract the request abstraction layer (TilesRequestContext etc.), a real "framework in the framework" that will become a first-class-citizen. Consider the merge with Scopes.
• Refactor the template-common layer to use the request abstraction framework. This way, the code will be mostly in this layer; the technology-specific code will be only an adaptation layer. Consider automatic generation of tags.