No idea - unless all options are selected and the form's method is a GET...
but even in that case you'd get some exceptions.
So, it sounds best if you could open an issue for this - preferably
attaching some
sources that recreate this (a zip of a maven project that
someone can mvn jetty:run)
On
Doubling my follow-up, by eliminating form fields one at a time I determined
that the problem was somewhat inexplicably caused by the number of
selections in one of the fields. In its default state, some 2900 options
appear in this one select field. I'm hard pressed to explain why, but this
quant
andyman32 wrote:
>
> ... I have tried changing the action, I have tried a simple sample form,
> no luck.
>
Correction: I created a very basic implementation of a form in this same
app, using the precise same pattern, and it did invoke the doPerformSearch(
IRequestCycle ) method when the form
