WicketTester and FormTester came from a draft design in my team. FormTester is not designed for reuse because in early stage, we have found it's hard to figure out what parameters hold by MockServletRequest after several submission.
To enforce resetting parameters for each submission, we seperate FormTester from WicketTester and it always call setupRequestAndResponse() while construction. This also reduces complexity of WicketTester API. But these are just early story. On Dec 19, 2007 6:38 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > I can't reuse the FormTester to do multiple submits. From the > documentation > it seems that this is by design. I may be slow today, but this seems like > something that was added but not completed. > Can anyone elaborate why the form tester needs to be re-created after each > submission? I can't think of a reason. > Another thing I don't like about the form tester is that it is separate > from > the WicketTester. Why a separate concept? > > Martijn > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0-rc2 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/ > -- Ingram Chen online share order: http://dinbendon.net blog: http://www.javaworld.com.tw/roller/page/ingramchen
