Re: Wicket and Reverse Proxy

Makes sense, but I need to override this behavior. Is there a way to stop Wicket from sending the elements at the time of the AJAX response? On Fri, Mar 26, 2010 at 9:52 AM, Igor Vaynberg wrote: > because wicket doesnt track what has been "sent" or not, it simply > rend

Re: Wicket and Reverse Proxy

because wicket doesnt track what has been "sent" or not, it simply renders what you tell it to. the filtering of duplicates happens on the client side where js knows whats is there and what is not. -igor On Fri, Mar 26, 2010 at 5:53 AM, T Ames wrote: > H... No responses.  Maybe I can attack

Re: Wicket and Reverse Proxy

H... No responses. Maybe I can attack this little by little. When an AJAX response is sent back to the browser, is there a way to stop Wicket from sending the elements? These