Component initialization

[kranga <kr...@k2d2.org>]

Is there a way to ensure that a component is properly initialized() (similar
to initialize() method for pages?). Are components pooled the same way as
pages? I have an arrayList in a component that should be cleared before use
in a request cycle? How do I guarantee that?

Thanks


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

Re: Component initialization

[Bryan Lewis <br...@maine.rr.com>]

I don't believe components are pooled.  A component's instance variable
would not be retained from one use to the next.  (Nor would a non-persistent
property be stored in the session, of course.)  It's an easy thing to verify
though.



----- Original Message ----- 
From: "kranga" <kr...@k2d2.org>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Wednesday, January 05, 2005 10:23 PM
Subject: Component initialization


> Is there a way to ensure that a component is properly initialized()
(similar
> to initialize() method for pages?). Are components pooled the same way as
> pages? I have an arrayList in a component that should be cleared before
use
> in a request cycle? How do I guarantee that?
>
> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>


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