Maybe Tapestry needs to render the whole loop internally first in order to know how to persist the loop in hidden fields. Perhaps setting volatile=true on the loop helps?
On Mon, 28 Aug 2006 14:24:59 +0200, Rodnei Couto <[EMAIL PROTECTED]> wrote: > I´m using tapestry 4.0.2 and i am having problems with OutOfMemory > exceptions generating some VERY big reports (more than 10000 elements). > > I searched in the maillist but didn´t find any solution: > http://marc2.theaimsgroup.com/?l=tapestry-user&m=112864214530411&w=2 > > The report page is quite simple. Just a "for" with a custom component > inside to generate de HTML output inside a table. Using a Memory > Profiler i found out that all the generation of the report went fine and > when tapestry started rendering it reached 300 MB of memory with no > output to the browser. After every thing was rendered the memory stared > to go down and tapestry starded to output to the browser. > > Is there any way of outputing to the browser on fly? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
