Problem comes from 3rd party library that does some extra actions along applet's 3 requests. Library actions trigger extra GET requests for a whole page ( for example http://server/app/?2 ), Which are the reason of StalePageException during calling javascript from applet.
I must still debug to see what really triggers these GETs. Thanks for the help Martin. Best regards, Michal Wegrzyn > -----Original Message----- > From: Martin Grigorov [mailto:mgrigo...@apache.org] > Sent: Monday, November 26, 2012 14:03 > To: users@wicket.apache.org > Subject: Re: multiple requests and StalePageException > > The renderCount increases only when you use non-Ajax requests, i.e. > when you re-render the whole page. > Make sure that "executes Wicket behavior via js" uses Wicket.Ajax.** > > > On Mon, Nov 26, 2012 at 1:56 PM, Michal Wegrzyn > <michal.wegr...@onior.com>wrote: > > > Hi group, > > > > In my Wicket application I have an applet. In the background it > > requests servlet and finally executes Wicket behavior via js. > > If one request is performed, then everything works without problems. > > > > Lately I have changed applet and now it can do one or three requests. > > If it performs three requests then StalePageException is thrown, > which > > causes page refreshed and that is not a desired behavior. > > When I debug difference between render counter and page counter is > > exactly 2, so I think that issue is connected with two "extra" applet > requests. > > > > Do I miss something on the Wicket side? If not, what is the best way > > to avoid StalePageException in this case? > > > > Best regards, > > Michal Wegrzyn > > > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com <http://jweekend.com/>
