You're probably experiencing double clicks on your ajax buttons. When the second request reaches the button, is is already disabled again.
Check this: http://wicketinaction.com/2008/12/preventing-double-ajax-requests-in-3-lines-of-code/ Sven On 10/16/2012 06:24 PM, eugenebalt wrote:
Hi, Sorry, I have to bump thread back up again. We still have no clear idea how to address this issue, which only happens sporadically on our production server (and we can't reproduce it locally). We have screens with Ajax Buttons which submit forms, but also disable/hide these Ajax buttons. I am guessing, based on earlier answers, that sometimes, the disable/hide happens *BEFORE* the Form Submit, and Wicket doesn't like that. Wicket requires that all form fields be enabled and visible to ensure form integrity. The simplest question is, how do we turn off this check in Wicket, or how do we guard against this error? "Submit button is not visible" or "Submit button is enabled". We can't rewrite our app from scratch, it has a lot of screens and a lot of functionality, we do need to toggle these buttons when submitting the form. Please, any help would be appreciated. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180p4653012.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
