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. You can use PageLink component in many contexts and each time you
need to specify the destination page. So you use the "page" parameter
and assign it through the component binding and the tag attribute. This
parameter is then "internally" bound to one of the PageLink properties,
but you as a component user need not be aware of that.
Hope it clears some foggy... =)
Ivano Pagano.
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]
