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
quantity of options simply "breaks" the Tapestry form processing mechanism.
No exceptions, it simply seems to go batty. I would like to be able to
handle this full list with Tapestry; it works just fine in raw j2ee. So, a
bit of a mystery remains - is there a limit to the number of options a
Select object in Tapestry can handle? And, if this conceptual limit is lower
than 2900, why does it not throw any kind of notice or error, but simply
"gives up the ghost" and returns to Home? I am a total n00b...
andyman32 wrote:
>
> Hi, I'm hoping I'm missing something very simple here. I'm putting
> together a reporting app that uses an elaborate search form to mine some
> data and run some stats. The form fields are interdependent; selecting a
> value in one refreshes the page and updates the value in the next. I had
> this working quite smoothly a few days ago, then, suddenly and
> mysteriously, I hit quite an odd problem: the form no longer executes the
> listener action in the Page class that contains it. It literally is the
> same page, same code, same method.
>
> Now, whenever I submit this form, the listener is not called, but the
> servlet returns me to the Home page. I have tried changing the action, I
> have tried a simple sample form, no luck. The fact that it navigates back
> to the Home page every request-response cycle is secondary to the fact
> that it NEVER INVOKES THE LISTENER METHOD.
>
> Here's a snippet from SearchForm.html:
>
>
> <form jwcid="[EMAIL PROTECTED]" listener="listener:doPerformSearch">
> (form fields)
> <input type="submit" value="Search" />
> </form>
>
>
> Here's a snippet from the underlying class, SearchFormPage.java:
>
> public abstract class SearchFormPage extends BasePage implements
> IActionListener
> {
> public void doPerformSearch( IRequestCycle cycle )
> {
> log.error( "doing perform search..." );
> // do stuff
> }
>
> public void actionTriggered( IComponent component, IRequestCycle cycle )
> {
> log.error( "action triggered..." );
> // do stuff
> }
> }
>
> Neither log message is ever printed out. In fact, NO error whatsoever is
> printed out. No exceptions. The form is simply ignored - dropped - and the
> r-r cycle is sent to Home.
>
> Any ideas? What might I have inadvertently changed? Is this not an
> acceptable implementation - or is the tapestry form tag wrong? Doesn't
> listener="listener:doPerformSearch" mean that the doPerformSearch(
> IRequestCycle cycle ) method should be invoked?
>
> Thanks in advance for any advice... I'm really going out of my mind here
> checking old versions in CVS and trying to figure out what changed without
> my noticing it.
>
> -Andy
>
>
--
View this message in context:
http://www.nabble.com/Form-Navigation-Issue-with-Tapestry-4.1.5-tp20292572p20294026.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
