Hi Lucas,
I think it's a bug, because in my case I have a from when i set values of
some component, then i execute ajaw event to submit the form, wickettester
execute what i want, but after that if i submit the form with
formTester.submit('path'); i'm getting the same the result as if clicked on
th
Thanks for the reply.
I wasn't aware that values are consumed after an ajax request.
My bad.
Thanks for taking the time to reply. It really does make a difference.
Regards,
Lucas
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WicketTester-executeAjaxEvent-causes-p
I thought that someone moderates my responses but No, they are published:
http://markmail.org/message/e5qhl5nlo2nlwmeh
Since 6.16.0 you can do:
formTester.setValue() // value is set
formTester.setValue() // value is set
formTester.submit(pathToAjaxSubmitter) // values are submitted and consumed
M
Hi,
everytime WicketTester processes a request, all previously set values
are consumed, i.e. no longer present for the next request.
formTester.setValue() // value is set
wicketTester.executeAjaxEvent() // values are consumed
formTester.submit() // no values
wicketTester.executeAjaxEvent() //
Dear Forum,
I have come across a strange behaviour when running
wicketTester.executeAjaxEvent and FormTester on form fields with
setRequired( true );
If I call formTester.setValue(), followed by
wicketTester.executeAjaxEvent(), followed by formTester.submit(), the values
on the form fields are cle
