Sitemesh is fine if you only have one "changable" component on your page. If you need more than one component on your page you could use the Include tag to include as many content areas as you want which you can define in your xwork.xml. The include tag can look at the value stack to decide what page to include. Using the static parameter interceptor you can set the property on your action from your config.
----- Original Message ----- From: "Anoop Ranganath" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 18, 2003 7:14 PM Subject: [OS-webwork] velocity, layouts, and flow > I'm beginning work on my velocity templates for my ww2 app, and I'm > having a bit of an issue. Ideally, I'd have a template that contains > my header and footer, and then a token that inserts the appropriate > screen into it. > > In my xwork.xml, I would have a result that points to screen1.vm, and > screen would be inserted into my layout. > > As it stands, it looks like I will have to include the header at the > top of everyone of my screens and include the footer at the bottom. My > other option would be have one velocity template that takes a parameter > which is the screenname, and then icnludes that. that'd be pretty ugly > also, in that I can't just make the result the destination screen. > > Any ideas on the best way to skin this cat? > > Anoop > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
