Wicket 1.4.1 resolved my issue.
I still had fun tracing through the wicket code though. It's pristine in
there.
--pete
Ooops, my last statement was not correct. The correct form values from my
FormTester are posted on the request, but the form processing takes place
for form-2 on the server side.
--pete
Okay, I'm on the trail of what is happening, but don't have the full answer
yet. I doubt this is a defect, but rather a misuse of nested forms & ajax
components on my part. Though I don't feel like I know enough about wicket
to make the call.
What I know is: the wrong AjaxButton is being selecte
Thank you for the reply!
On your advice, I took a step back and created a new page, form, and
ajaxbutton. Creating a FormTester and using executeAjaxEvent(...) does
indeed submit the form through via standard form processing! However, it's
still not happening on my original page. I'm looking in
> The simple question I have is, "How do I invoke the behavior associated
> with an AjaxButton as well as the form processing logic, like validation?"
Clicking the button always results in form processing if you hae
defaultFormProcessing=true.
You can click the button via ajax using tester.execut
Hello everyone!
I have read a lot of forum posts and defects/feature requests around testing
form posts with ajax and am still confused. The simple question I have is,
"How do I invoke the behavior associated with an AjaxButton as well as the
form processing logic, like validation?" An even simp
