what servlet container are you using? i think this problem popped up
on weblogic before and was due to a combination of a weblogic bug and
the particular servlet mapping that was used.

does the behavior happen to all form components or just some
particular one? try it without that funky onerror() override.

-igor

On 11/2/07, Chris Colman <[EMAIL PROTECTED]> wrote:
> > can you make sure your servlet mapping is of form /foo/*
> >
> > -igor
>
> Yes it's of that form.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to