On Sun, 13 Jul 2003, John Patterson wrote: > > > <page:applyDecorator name="panel" page="foo.action" /> > > > > foo.action can do whatever it wants. It can also be controlled from > > information from the session if you like. Lo and behold. > > > > I assume that you mean you would include two such tags from within the > template page like this: > > <html> > <body> > <page:applyDecorator name="panel" page="foo.action" /> > <br> > <page:applyDecorator name="panel" page="bar.action" /> > </body> > </html> > > and then use the foo and bar actions to figure out what content to include. > How can this same template be reused by a diferent page to dispaly > differnent content?
foo and bar certainly have access to state, do they not? > I would not consider using request parameters or session state to make this > choice an adequate solution. Really? Why? Request state works just as well as session state in this system; if you have an objection to those, well... I'd love to see why, since they don't get clustered or have the overhead of other mechanisms. What's more, decorators are really fundamentally simple and very easy to control in many ways, so to me, a lot of your objection or confusion seems strange; if you're fixated on Tiles, please use it. Nobody that I know of will hunt you down with torches or tar and feathers. Chances are, nobody will really care; we know how to get SiteMesh to do the same sort of thing in many ways (since it really puts very few limitations on you) and you don't see it; it's okay. ------------------------------------------------------------------- Joseph B. Ottinger http://enigmastation.com IT Consultant [EMAIL PROTECTED] J2EE Editor - Java Developer's Journal [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
