Ray, I don't understand why you say you must tie a form name into a URL call. Can you give /webapp/XXX relative URL examles to help us make more sense of what you are doing?
Regards, David -----Original Message----- From: Ray Madigan [mailto:[EMAIL PROTECTED] Sent: Thursday, March 24, 2005 5:03 PM To: 'Struts Users Mailing List' Subject: Tiles-defs and Forms I think I am having an understanding problem of how to tie tiles and tile defs with struts forms. My application uses a classicLayout type definition that looks just like the one shipps with struts. It has a body and a menu section. My problem is as follows. My menu jsp has a set of attributes that sets a context for the pages that will show in the body section. So the body needs attributes that were determined by the menu element that was selected. To make this work it seems like I need one form that covers both the menu and the body sections of the page. To compilcate things the menu can work for several different body sections and the code was originally written when the application used frames. With frames I could have a seperate form for each frame so the body and the menu were not connected except for the Url's that were executed contained the context for the body that would service the request. With one form per jsp page, the menu needs to reference the form to create the url's for the body, and the body needs to reference the form for the context for the body. The problem is then the menu needs to know the name of the form. With several different forms I don't see how to manage this. I can see several choices: 1) One large form to cover all possible cases, It would have to have a large number of attributes. 2) A form for each set of body jsp's and a special bean in the Session attribute scope to maintain the page context. 3) A seperate instance of the navigate jsp for each set of body jsp's. Currently there is about 20 sets of body contexts with 5 to 20 pages per body context. In the future this could get larger. Has anyone figured out how to do this? Is there a best practices model for this situation? Any help would be appareciated. Thanks in advance --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
