You should be able to do that. In-fact, that's one of the ways to re-use common page presentations. If you do your job write, then your main page is composed of a bunch of includes to render different parts of the result "tree". Be-careful, however, the last time I checked the nested tags only work well in a static include scenario. They don't work well with dynamic includes, which is what you might find you need to do, if you have a lot of conditionals (otherwise, it's very easy to exceed to the 64K method limit).
-AP_ http://www.alexparansky.com Java/J2EE Architect/Consultant http://www.myprofiles.com/member/view.do?profileId=127 -----Original Message----- From: Kousek, Theron [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11, 2002 2:33 PM To: 'Struts Users Mailing List' Subject: nested tags question Hi folks: I have a few forms that contain the same type of "template"... I want to create a generic template that uses a form bean. This template needs to handle form beans that are at the root level or a form bean that may be nested. So in one screen, the template will be at the root and not need to be nested. In another screen, the same template will need to be nested. So basically, I can contain my nested statements like: <nested:root name="clientForm"> <nested:nest property="billingForm"> outside the scope of the template and in the file that needs to invoke the template... The actual template can contain the : <td align="left"> <nested:text property="displayBillid" disabled="true" size="10" styleId="small"/> </td> type tags... So here's my question: Even if a form bean is at the root and not nested at all, can I still declare it to be nested, only define it at the root? So billingForm for example could be: <nested:root name="billingForm"> even if it is at the topmost level? Is this normal or should I avoid it? If this is legal, then I will be able to literally plug and play these templates into other screens and will have one common layout repository. thanks, Theron -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
