igor.vaynberg wrote: > > can you set a breakpoint and see where response.redirect is being called > from for ajax processing? i can see it would be called if you added the > page > itself to the ajaxrequesttarget. >
Actually, redirect seems to be false, but WebRequestCycle.isRedirect first checks for isAjax. It also has a comment "If it's an ajax request we always redirect." I can try to debug it later to confirm, if needed. igor.vaynberg wrote: > > as far as supporting stateless ajax goes, i am not sure if or when we are > going to support it. we are not going to look into it until we start > working > on 1.5 (a month or two). the focus of wicket has never been stateless > pages. > I understand; I was thinking that wicket already supports stateless pages, and they can help improve the performance a lot, and from my experiment I found that it's not really hard to make stateless ajax work. Anyway, it's not bad if wicket will support that in a few months. Until then, I wonder if my way of doing it is good. Adrian -- View this message in context: http://www.nabble.com/Stateless-AJAX-links-tp20031309p20082568.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
