> Could you give us an example of how to accomplish this?What we did is to extend the Form component with a flash-persist defaultTracker. We're using our Form component everywhere:public class Form extends org.apache.tapestry.corelib.components.Form{ @Persist("flash") private ValidationTracke
> By making it @Persist (i.e. with default), then the container (i.e., your> page) can set a @Meta to control the default persistence of components below> it. Thus, if you want the default to be "flash", you're in luck.So, you think every page in every T5 app in the world should override the defau
On Fri, 03 Aug 2007 16:07:07 -0300, Howard Lewis Ship <[EMAIL PROTECTED]>
wrote:
By making it @Persist (i.e. with default), then the container (i.e., your
page) can set a @Meta to control the default persistence of components
below it. Thus, if you want the default to be "flash", you're in
By making it @Persist (i.e. with default), then the container (i.e., your
page) can set a @Meta to control the default persistence of components below
it. Thus, if you want the default to be "flash", you're in luck. Or, you
can inject the Form component, it has methods that overlap
ValidationDele
Hi!
I was wondering why the "_defaultTracker" in the Form component is marked
as @Persist not as @Persist("flash").
In my opinion it should be @Persist("flash")!!
Persisting the ValidationTracker in the session leads to some (usually)
not wanted
behaviour: the validation is not reset, even thou
