This issue has bitten us also. Any idea on when the fix will be in? thanks
Matej Knopp-2 wrote: > > Okay, the problem here is that protlet support broke > CryptedUrlWebRequestCodingStrategy. > > -Matej > > On 10/16/07, Matej Knopp <[EMAIL PROTECTED]> wrote: >> There's no way removing onAttach() could cause such problems, as it >> was basically a noop. The onAttach() implementations were just empty. >> And if you had your onAttach implementation, you should get a >> compilation error as onAttach is now final. >> >> Are you sure you have cleared your browser cache when updating? >> >> -Matej >> >> On 10/16/07, Brandon Fuller <[EMAIL PROTECTED]> wrote: >> > >> > 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. >> > >> > >> > > -- View this message in context: http://www.nabble.com/Wicket-Beta4-and-Ajax-Links-tf4616750.html#a13435200 Sent from the Wicket - Dev mailing list archive at Nabble.com.
