Ajax Button sends new request to page instead of refreshing part of it
The Wicket AJAX debugger is helpful for this case. Look to see the XML you get back from the wicket request.
If you see something along the lines of “Page could not be rendered” instead of well-formatted XML, there was an error somewhere in the request cycle that wicket doesn’t bother giving you an error that is easy to see.
When this happened to me, it’s because my form model had problems converting data types (another weird error of it’s own that resulted in trying to use a Form that had a Date as the backing object – that’s another story, but I fixed it by using a bean with a Date instead of a Date as the model for the form).