Not sure why, but seems if I inject the regular ValidationTrackerImpl
implementation and don't persist it, I don't get null pointers anymore and
all seems to be well.
As an aside, using @Persist("client") is undesirable to me because of the
url parameter it was adding.
In T4, I sometimes used the
Maybe injecting the ValidationTracker in your page and persisting it
with @Persist("client:page") and then using the form's tracker parameter
to use this will work?
-Filip
Daniel Leffel skrev:
Is that done by setting clientValidation=true? I tried that and got the same
behavior.
Or did you m
Is that done by setting clientValidation=true? I tried that and got the same
behavior.
Or did you mean to store the validation tracker as a hidden element in the
form?
On 9/10/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
>
> You can store the validation tracker on the client side instead of t
You can store the validation tracker on the client side instead of the
server side.
On 9/10/07, Daniel Leffel <[EMAIL PROTECTED]> wrote:
>
> I realize client-side persistence isn't complete,so... Is there any way to
> turn off validation to make a form stateless? I tried implementing my own
> vali
I realize client-side persistence isn't complete,so... Is there any way to
turn off validation to make a form stateless? I tried implementing my own
validation tracker which ignores errors, but I get a null pointer exception.
Stack below:
-
org.apache.tapestry.internal.services.ComponentIn
