AFAIK, tapestry properties will be reset, unless you specify them persist.
If you want to reset also instance variables you use during the request
you should use the pageDetachListener interface (just implement it, no
need to addListener anywhere, tapestry will do that for you).
Cheers,
Ron
Alex Kartashev wrote:
Very nice analogy on Unix symlink! I think I understand now the concept
of a component parameter (the Users Guide is an invaluable resource
there, I must say).
What about the lifecyle of a component property? All I want to make sure
is that they will be reset once the containing page goes back to the pool.
Thanks,
Alex
Ron Piterman wrote:
just another thing : parameters function very much like symlinks in
linux/unix -
when you read them you actually read the target of the link, and when
you write to them you change the target of the link -
The important thing is where the link is pointing to -
this you decide in the <binding element.
Cheers,
Ron
Alex Kartashev wrote:
Hi guys,
I am a new Tapestry 4 user. I've been researching Tapestry 4 for
about a week now, even developed some toy apps. I am already sold on
the value proposition.
One thing I am a bit confused about is Component parameters and
properties.
1. Is there any difference between a component parameter and
property? Or are these words used interchangeably?
2. Whereas lifecycle of page properties is very clear: pages are
pooled and their properties are cleared out upon returning to the
pool, components are not pooled independently but along with their
pages. So, what about they properties/parameters? Will they be
cleared out automatically as well?
Thank a lot in advance,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
