Got it. Thank you very much!
Alex
Ron Piterman wrote:
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
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
Al
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
The difference is substantial:
Both Pages and Components have Properties associated which are set and
cleared for each instance.
Since you're reusing components inside pages and other containing
components you need to pass values that configure the inner component
for the individual use.
e.g
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
Hi guys,
I
parameters are like java method parameters
properties are like java instance variables.
How you configure them what Tapestry does with them is the magic.
geoff
On 3/1/06, Alex Kartashev <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> I am a new Tapestry 4 user. I've been researching Tapestry 4 for ab
properties are to maintain internal component state, while parameters
are the tying the component to its container.
properties are (in the simple case) a "shortcut" for implementing real
Pojo properties for your page/component - but they offer some extras,
like persistance -
parameters update