I recently took Wicketand built single page web applicationwith several tabs. I used the AjaxTabbedPanel , and each tab pretty much contains all of the Ajax input components. The problem is that I leave the application in standby mode for a minute (or a few seconds less) and click on another tab, the application does not fulfill my request until I repeat it a second time. As soon as I click a second time, the application normalizes in terms of tab navigation. Is this Wicket modelrelated to disconnecting and creating a new model? Can someone advise me on any way to fix this so that I can navigate the tabs without being limited by any time constraints.
UPDATED
I see the same problem on the wicket example page. Please check the link below. If you first select the “second tab” and leave the page inactive for at least a couple of minutes, and then if you click the “third tab”, it will either remain on the “second tab” or go to the “first tab”. If you click on the "third tab" again, then it will work, but again until it becomes inactive. You will see the same problem again and again when the page is idle.
examples6x.wicket.apache.org/ajax/tabbed-panel
source
share