Blank form prob means empty model objects. Start Wicket in DEVELOPMENT mode: https://cwiki.apache.org/WICKET/faqs.html#FAQs-Myapplicationsays%2522DEVELOPMENTMODE%2522%252ChowdoIswitchtoproduction%253F
Add the DebugBar to your page: http://ci.apache.org/projects/wicket/apidocs/6.x/org/apache/wicket/devutils/debugbar/DebugBar.html Then analyze the output in the AjaxConsole (lower right corner of your screen). You should see all the AJAX replies from the server to your browser. You can also use breakpoints and figure out what's going on in your Java code on the server side. Read up on Wicket and AJAX in chapter 16 of the Wicket Free Guide at: http://wicket.apache.org/learn/books/ Have a great day, Paul Bors On Jun 20, 2013, at 4:54 PM, Paul Bors <[email protected]> wrote: > Stack trace? > > -----Original Message----- > From: Marios Skounakis [mailto:[email protected]] > Sent: Thursday, June 20, 2013 4:12 PM > To: [email protected] > Subject: Ajax form submit and Tomcat maxPostSize/connectionTimeout > > Hi all, > > I have the following problem: > - User submits form with lots of textareas via ajax > - User gets a blank page > > I think (but I'm not quite sure yet) this happens when the textareas contain > so much text that either maxPostSize or connectionTimeout (submit tries to > store to db as well) are exceeded. > > The weird thing is that there is no exception. The form comes back after the > ajax request with blank components. > > Has anyone else seen this behavior? Why is there no exception? > > Thanks > Marios >
