Tiles Library Features Overview
Following is an overview of what can be done with Tiles : Screen definitions Create a screen by assembling *Tiles* : header, footer, menu, body Definitions can take place : in a centralized xml file directly in jsp page in struts action Definitions provide an inheritance mechanism : a definition can extends another one, and override parameters. Templating *Tiles* framework is entirely compatible with Templates defined by David Geary and implemented in Struts You can replace Templates library by *Tiles* one Layouts Define common page layouts and reuse them across your web site Define menu layouts, and use them by passing lists of items and links Define portal layout, use it by passing list of *Tiles* (pages) to show Reuse existing layouts, or define your owns Dynamic page building Tiles are gather dynamically during page reload. It is possible to change any attributes : layout, list of Tiles in portal, list of menu items, ... Reuse of *Tiles* / Components If well defined, a *Tile* can be reused in different location Dynamic attributes are used to parameterized Tiles It is possible to define library of reusable Tiles. Build a page by assembling predefined components, give them appropriate parameters Internationalization (i18n) It is possible to load different tiles according to Locale A mechanism similar to Java properties files is used for definitions files : you can have one definition file per Locale. The appropriate definition is loaded according to current Locale Multi-channels It is possible to load different Tiles according to a key stored in jsp session, or anywhere. For example, key could be user provilege, browser type, ... A mechanism similar to Java properties files is used for definitions files : you can have one definition file per key. The appropriate definition is loaded according to the key.

Tiles Library
Features Overview

Following is an overview of what can be done with Tiles :

Screen definitions
- Create a screen by assembling Tiles : header, footer, menu, body
- Definitions can take place :
  - in a centralized xml file
  - directly in jsp page
  - in struts action
- Definitions provide an inheritance mechanism : a definition can extends another one, and override parameters.
Templating
- Tiles framework is entirely compatible with Templates defined by David Geary and implemented in Struts
- You can replace Templates library by Tiles one
Layouts
- Define common page layouts and reuse them across your web site
- Define menu layouts, and use them by passing lists of items and links
- Define portal layout, use it by passing list of Tiles (pages) to show
- Reuse existing layouts, or define your owns
Dynamic page building
- Tiles are gather dynamically during page reload. It is possible to change any attributes : layout, list of Tiles in portal, list of menu items, ...
Reuse of Tiles / Components
- If well defined, a Tile can be reused in different location
- Dynamic attributes are used to parameterized Tiles
- It is possible to define library of reusable Tiles.
- Build a page by assembling predefined components, give them appropriate parameters
Internationalization (i18n)

It is possible to load different tiles according to Locale
A mechanism similar to Java properties files is used for definitions files : you can have one definition file per Locale. The appropriate definition is loaded according to current Locale

Multi-channels

It is possible to load different Tiles according to a key stored in jsp session, or anywhere.
For example, key could be user provilege, browser type, ...
A mechanism similar to Java properties files is used for definitions files : you can have one definition file per key. The appropriate definition is loaded according to the key.