For your second question I believe the answer is to create a new tiles definition where you override the menu tile. In your action reference the new definition.
But your first question I don't know. I am now building my first large corporate struts app and am using tiles which I like very much but am very worried about speed and wonder whether I should use frames to speed things up( for your re-gen reasons as well as the caching of images, javascript ref tables, etc on a fixed frame such as navbar). So I am curious how tiles would run on top of frames and whether I should consider it. ----- Original Message ----- From: "Carl Hope" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Sunday, January 19, 2003 9:07 AM Subject: Struts / Tiles Design question I'm recoding an existing app using Struts and Tiles. The app originally used frames with the usual components of header, menu, body and footer. I've replaced the frameset with a layout template and it works fine. The difficulty I'm having is when I only want to refresh the menu tile and not repeat all the work to create the body. e.g. the user clicks on an image in the menu that opens up a tree node to show sub-menus - only the menu model and view are changed. With frames this was easy, but with Tiles it's not so easy, at least not for me. There are two problems: - Is there a way to process just the menu HTML and avoid re-generating the body, header and footer?. - If all tiles must be regenerated, how should I define the Action for the menu change. This should really just call a menu handler page but if the entire page must be regenerated, then I need to specify the action for the current Tiles definition and retain state. I've considered trappping and caching the generated HTML from each response and replacing only the changed menu but that doesn't seem "clean". Anyone have any guidance? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
