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 selected as the
submittingComponent in Form.findSubmittingButton().
I have the following nesting:
panel-A
form-1
AjaxButton (foo)
panel-B
form-2
AjaxButton (bar)
I'm calling executeAjaxEvent on 'foo', but it is not the first AjaxButton
encountered during my pages visitChildren(). At least in my situation, the
first AjaxButton encountered is 'bar' and it's selected and returned as
submittingComponent. This seems to cause form-2 to be posted on the
request.
Any thoughts on this would be greatly appreciated!
--pete
