On Sun, 20 May 2012 06:08:09 -0300, Muhammad Gelbana
wrote:
Is having 46 select component generated by a loop, a big thing ? It's a
dashboard page.
From me thinking as an user, 46 fields in the same form is way too many
fields . . .
--
Thiago H. de Paula Figueiredo
Independent Java, Apa
No they are just strings and I read the submitted values from in injected
request object because the number of select components is dynamic and may
change. I wrote this form a very long time ago and wanted to be very
tapestry oriented but I think I don't need the tapestry select components
here !
Typically, that occurs when the values inside the Selects are
Serializable, but not HIbernate entities. Tapestry serializes them
which gets very verbose. Take a close look at the objects being
stored as values, and the encoder parameter of the Select component.
On Sun, May 20, 2012 at 2:08 AM, Mu
Is having 46 select component generated by a loop, a big thing ? It's a
dashboard page.
On Thu, May 10, 2012 at 7:04 PM, Howard Lewis Ship wrote:
> I can say that it has something to do with encoding data into a
> rendering Form (the "t:formdata" hidden field).
>
> Is it possible you have an ve
I can say that it has something to do with encoding data into a
rendering Form (the "t:formdata" hidden field).
Is it possible you have an very, very, very large form (possibly an
infinite loop)?
Somewhere in your console, there should be an operations trace from
Tapestry that may shed more light
On Thu, 10 May 2012 06:14:10 -0300, Muhammad Gelbana
wrote:
This exception is thrown in the logs randomly and I can't track it ! It
looks like tapestry failed to do something but It must be something in my
code, although the stacktrace isn't helping.
java.lang.OutOfMemoryError
at java.util
