On 11/16/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > Keith Sader wrote:
> I'm not sure exactly what you meant by 'polymorphism off of a submit' so > this might be completely off-base but... Passing the action into the > tile definition may be one option, depending on how your tiles and > actions are set up. Another option may be to wait for the Struts 1.3 > release that's coming up. 1.3 lets you have 'extends' relationships > between various configuration elements. I'm not sure, but I think this > includes tiles definitions, in which case you can have a tile for each > of your 'precedence levels' with each extending the higer-level one. > > If that doesn't sound like it might be useful, I probably haven't > understood what you want to achieve properly. Thanks for your input, but (as usual) I've found out what my real issue is. I was defining the <form> element inside of the tile when the containing page needs to contain the form instead of the tile. I'm going to refactor the tile to be just the html elements and inputs that are common to all these pages and put the form in the containing page. What I was working on at first was <other inputs> <tile form> but this wouldn't have worked on a submit so what I'll put in now is: <form> <other inputs> <tile inputs> </form> Now I just need to eliminate some action duplication. thanks, -- Keith Sader [EMAIL PROTECTED] http://www.saderfamily.org/roller/page/ksader http://www.jroller.com/page/certifieddanger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
