In my opinion never use @Persist in a reusable component. We have it in Grid
and it does create a problem when there are multiple grids on a page. Besides
you don't want a session at times and Grid doesn't help.
Pages can have @Persist e.g. you have a search page where you want the search
crite
On Thu, Jan 3, 2013 at 5:12 PM, Alex Kotchnev wrote:
> Now, as far as I understand, @Persist("session") stores the value in the
> session, keyed on the component class (e.g. thus in component A, a field
> "@Persist private String fooMessage" would/could store a different value
> than "@Persist p
Taha - thanks for your comments.
I was also building the application w/ almost no usage of @Persist in my
code. Then, when I started collaborating w/ another developer, he
introduced it in a couple of places. My initial reaction was to remove
them, but that's the time I realized that I didn't have
Hi Alex
Consider this not as an answer but as a comment :)
I think the more I understand tapestry the less I used @Persist. I take it as a
challenge to minimize the use of @Persist and even have a count of number of
@Persist's I am using in a given application. I use context and have been able
