Hi richard, thx for the reply. our application is what you described in the last paragrapgh of your reply. We predefine the components that can be displayed on a particular page. The users can choose only a subset of those. As you said, we know the set of componentes in a particular page at dev and deployment time itself.
i guess i would have to dig into @Block/@RenderBlock, @Conditional Tapestry Components and application custom components. We used a common action and a jsp tag to display the page based on the user's selection. if you have already done something similar to this, can you give some hints or directions about how to do this. regards ashok On 10/25/05, Hensley, Richard <[EMAIL PROTECTED]> wrote: > > Ashok, > > If I read your e-mail correctly, you had something of a portal type system > going. In general, Tapestry is based on the notion of static page > structure > to produce dynamic page content. Which is different from a portal, which > is > based on dynamic page structure to produce dynamic page content. > > In practical terms, this means that you need to know your page > specification > before you start rendering the page. The normal way to do this in tapestry > is with page specifications, page controller classes, and html templates. > There has also been folks on the list that have gone down the route of > extending the page specification source services to modify the > specifications on the fly. This might be an option for you. I'm not an > expert in the area, so I would not be able to help you. Another option you > might consider is using a Portlet server, and constructing your content in > terms of portlets using Tapestry. > > If, on the other hand, you simply have a highly configurable user > interface > with known set of components that can be selected by the user, I would > investigate the @Block/@RenderBlock and @Conditional Tapestry Components > used in conjuction with application custom components. We have been able > to > build a very user configurable user interface using the basic tools > supplied > by Tapestry. This works great if the repository of available components is > known at application development and deployment time. If the components > can > be developed on the fly after deployment, you have a portal type > situation, > see above. > > Richard > > -----Original Message----- > From: Ashok Madhavan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 25, 2005 8:39 AM > To: [email protected] > Subject: Tapestry Newbie Question > > Hi all, > i have just started paying with Tapestry. > > we have a application which was written in struts. In each page in our > application we specified the components ( like Status Chart, My Action > items > etc ) that can be rendered. These components are stored in DB as xml. > There > will one page definition xml per page. The user can choose which > component > needed to be rendered. We had a common page which did a dynamic > jsp:include > to include the appropriate components. > > If i were to do this / convert to Tapestry how would i do it. Also how > do i > do include another page dynamically in tapestry. > > regards > Ashok Madhavan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
