Component initialization (when retrieving from pool?)

[Karthik Abram <ka...@neovera.com>]

Is there a method similar to page's initialize()that gets called for
components so that the members can be correctly initialized when retrieved
from the pool? Is this even a concern for components?


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: Component initialization (when retrieving from pool?)

[Kent Tong <ke...@cpttm.org.mo>]

Karthik Abram <karthik.abram <at> neovera.com> writes:

> 
> Is there a method similar to page's initialize()that gets called for
> components so that the members can be correctly initialized when retrieved
> from the pool? Is this even a concern for components?

Why not just use a <property-specification>? If you need
to get notified when the containing page is detached,
you can let your component implement IPageDetachListener
and add itself as a listener to the page.




---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org