Hi I agree that the original Poster seems not to have 'grokked' components yet and is looking around for an include mechanism.
Perhaps we need some Wiki postings to explain how to achieve common tasks with Tapestry with explicit reference to their JSP/Struts equivalent. On top of this can we come up with a 'lite' implementation strategy for new Tapestry users or those developing departmental apps which won't have a large number of users, won't be clustered and for whom the notion of tuning persistent page or component properties is overkill, such as special component and page subclasses or a runtime enhancement strategy that persists all programmer declared properties (perhaps via setter/getter enhancement a la hibernate) into the session. Mike On Wednesday, July 20, 2005, at 08:11AM, Larry Sherrill <[EMAIL PROTECTED]> wrote: > >Maybe I am misunderstanding the problem but why can't >the dynamic side menu and the dynamic top menu be >components that you define (via jwc-java-html). These >could be reused in different pages, accomplishing the >same end goal as your jsp include. > > >--- Preston CRAWFORD <[EMAIL PROTECTED]> >wrote: > ><<#3 - Regarding includes. We have the need to have >items like a dynamic >sde menu, a dynamic top menu. Items that will be >reused over and over >again. And this could just be a lack of understanding >of the Tapestry >mindset, but we just haven't been able to figure out >how to accomplish >this.>> > > > > > > >__________________________________ >Do you Yahoo!? >Yahoo! Mail - Helps protect you from nasty viruses. >http://promotions.yahoo.com/new_mail > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
