1. In each Action class, instead of setting the ActionForward to a page, set it to one common tiles definition AND set an attribute named 'forwardPage' in the request specifying the old ActionForward's path - /mymodule/whatever.jsp.
You can create one common tiles definition that specifies your header, menu, body, footer etc plus anything in particular like message keys (which I use to pass the browser window title to the layout page).
Then each page's tiles definition inherits from the common one so that you don't need to repeat anything. Anything different just overrides the common one's definition.
So therefore your ActionForward is the tiles definition for the page, not the common one. The definition specifies specific stuff for the page and inherits common stuff.
So you would have a common layout jsp, a few common jsps for menus, footers etc and one tile/jsp for each actual page in your site map.
And the common jsps can always be customized by passing them attributes.
NB if you use a common layout as the skeleton HTML page with <tiles:insert>s where the other tiles should go, you would have to nest the <tiles:put>s there to ensure that your attributes are passed on - by default they are not global. A gotcha that got me.
Adam -- struts 1.1 + tomcat 5.0.14 + java 1.4.2 Linux 2.4.20 RH9
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
