I removed the @Body from the page and now the output seems to be working
fine. The report is being outputed onfly as each component is rendered.
I guess the problem was really the buffer in the tag Body.
Thanks,
Rodnei Couto
Henri Dupre escreveu:
On 8/28/06, andyhot <[EMAIL PROTECTED]> wrote:
Henri Dupre wrote:
> On 8/28/06, Rodnei Couto <[EMAIL PROTECTED]> wrote:
>>
>> I did this and it didn't work.... it seems that Tapestry still
does not
>> send the html to the browser...
>>
>> Is it expected that Tapestry will render everything before sending
the
>> output to the browser?
>
>
> This is quite strange... what do you have inside your loop? I suspect
> that
> these components could be optimized.
> Tapestry 4 doesn't buffer and it sends the output straight to the
> browser.
if you're using @Body, it does buffer... it needs to gather all
contributed javascript
and render them in the correct places.
Actually even in the case of buffering, I'd be surprised that it is the
output that is really causing the out of memory.
I don't know what is the -Xmx parameter used but a fair guess is that
there
would be at least 100 mb of memory free?
Even with 10000 elements, 100 mb would be really alot.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
