Close. The ProgressiveDisplay will send a series of Ajax requests to the application to render, in your case, each subtopic.
The issue is that one server side, you have to know which subtopic to actually render. Much like an ActionLink, you can pass a context value (or values) to the PD; it fires an event (check the docs) to inform you what the context is before it renders its body. This gives you a chance to use those values to set up the page's state in readiness for the rendering. On Fri, Mar 5, 2010 at 11:43 AM, Henry Chen <hc...@peacocknine.com> wrote: > > I just figured it out. The error was caused by a nested loop component in the > ProgressiveDisplay and was not set to persist. > -- > View this message in context: > http://n2.nabble.com/Render-large-page-tp4677583p4682975.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
