Woah, sorry, i messed up that subject line (missed the RE: ), so if
you're looking for the original post, its:
http://mail-archives.apache.org/mod_mbox/tapestry-users/200709.mbox/[EMAIL
PROTECTED]
On 9/12/07, lasitha <[EMAIL PROTECTED]> wrote:
> Marcus, you mentioned offline you'd gotten this to
Marcus, you mentioned offline you'd gotten this to work by setting the
Loop component's 'volatile' parameter to true. I've scanned the
source and must admit i don't quite understand how the component is
designed to work when _not_ volatile. If anyone's had any success
updating state within a non-
Nick,
that was really simple ... and works fine, thank you.
But I must admit that I don't understand what I'm doing here (even
reading the documentation about loop.volatile did not help me, sorry).
What is volatile's default for?
I understood so far:
Having volatile=default causes serialization
Use:
Cheers,
Nick.
Marcus Schmidke wrote:
Hello all,
the following might be an absolute beginner's error, but since I'm an
absolute beginner, I probably am allowed to have this kind of problem
...
I'm trying to edit a list of values:
class Value {
String name;
String text;
boolean us
Hello all,
the following might be an absolute beginner's error, but since I'm an
absolute beginner, I probably am allowed to have this kind of problem
...
I'm trying to edit a list of values:
class Value {
String name;
String text;
boolean used;
... getters ...
... setters ...
}
class
