I seem to have stumbled onto the issue. I started looking through the history and I think the issue with ID WICKET-1059 broke the Ajax links, tabs, autocomplete, etc.
In my application, I obfuscate the URLs based on the FAQ article at: http://cwiki.apache.org/WICKET/obfuscating-urls.html#Obfuscatingurls-Wicket1.3 http://cwiki.apache.org/WICKET/obfuscating-urls.html#Obfuscatingurls-Wicket1.3 When I turn this off in my app, the Ajax links start working again as they did in beta3. I notice that WICKET-1059 did make edits on the WebRequestCodingStrategy and the AjaxRequestTarget. Its gotta be that combo. Not ready to dive in and fix it but this should help the developers isolate the issue and explain why some test cases do not see the issue. -- View this message in context: http://www.nabble.com/Wicket-Beta4-and-Ajax-Links-tf4616750.html#a13225366 Sent from the Wicket - Dev mailing list archive at Nabble.com.
