On 10/26/07, Norman Franke <[EMAIL PROTECTED]> wrote:
> The old @Foreach (Tapestry 4.0.x) did NOT do this, and I wish there
> was an option to do this with @For.
The old @Foreach is really just @For with volatile set to true
--
Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
Tapest
Hi Norman, thanks for the tips!
Studying a little bit the whole web app architecture I think I can use
the volatile attribute, since the data always come from a database and I
believe it´s never modified between form rendering and submission
(that's the most difficult thing to analyze), my coll
This really bugged me as well, since can easily add 100K to your page.
First, it only seems to happen inside a @Form component, as best as I
can tell from reading the docs. You can provide a "keyExpression" to
have it serialize the value of the object's attribute, e.g. it's
primary key for
Hi everybody !!
I'm having a little problem when using the @For component ... while I'm
iterating through the source collection the component prints a string
representation of the object as the value of the @For component, I went
to check the documentation and it says that the value attribute i
