It doesn't really matter where you clear it. Just clear it when you're done with it. As for the lifecycle question, you have to clear it because you @Persisted it. If you didn't @Persist it, you wouldn't have to clear it, but you'd likely lose your data when working with the form, depending on your workflow.
This should work fine. I do it all the time. -- Kevin On 5/17/08 12:34 PM, "Manuel Corrales" <[EMAIL PROTECTED]> wrote: > Hi Ned, the onSuccess methos is executed before the onSubmit, so that would > not work for me because i am doing the model logic on the onSubmit. I tryed > setting my variable in null after executing my businnes logic, but i still > have the same issue. My private variable should not be cleaned by Tapestry > pooling mechanism? > > The only thing i can think to fix this, is to set my variable to null after > the bussines logic, and then on the onACtivate method check if its null, the > i create a new one, if its not null then i do nothing. > > Thanks, and still waiting for an elegant solution to this ;) > ** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
