I almost fixed this yesterday but couldn't make up my mind without more
input from people.

Does anyone ~really~ care if the validation errors disappear when you
refresh the form? If not then it's as good as fixed tomorrow :)

On 3/8/06, Ben Dotte <bdotte@wide...> wrote:
>
> Hi Aj,
>
> This is essentially what the refresh listener on form is for; it
> bypasses client-side validation but unfortunately it does not bypass
> server-side validation right now. And if you call clearErrors() on your
> delegate in the refresh listener to get rid of the server-side errors,
> you end up losing any invalid data entered by the user. I have a bug
> open on this: http://issues.apache.org/jira/browse/TAPESTRY-867
>
> I'd love to hear if anyone else has found a workaround to this, but for
> now I have had to avoid doing this type of thing because of the way it
> works at present.
>
> HTH
> Ben
>
> -----Original Message-----
> From: Aj Gregory [mailto:ajgnet@u.wa...]
> Sent: Wednesday, March 08, 2006 2:05 PM
> To: Tapestry users
> Subject: Partial form submit
>
> I have a form and I'd like to include a @Submit with its own listener
> that I can use to submit part of the form and then after running the
> listener re-render the form so the user can then choose to submit with
> the listener defined for the @Form.
>
> For the most part this works except the validators for all the form
> fields complain because all of the fields aren't valid when the @Submit
> listener is clicked.  Is there a way to by pass the validation when the
> @Submit is clicked?
>
> Or is there a better way to do this in general?
>
> Thanks,
> -Aj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jaka...
> For additional commands, e-mail: tapestry-user-help@jaka...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jaka...
> For additional commands, e-mail: tapestry-user-help@jaka...
>
>