On Sat, Mar 31, 2012 at 6:22 PM, sudeivas <sureshkumar....@gmail.com> wrote: > I believe the best solution for me is to update my project to the latest > version of wicket, but still I am worried about the following issue, > > https://issues.apache.org/jira/browse/WICKET-4454 > > since lot of our code have nested components. Any idea when 1.5.6 will be > released? (so that I can wait for sometime and update to 1.5.6)
No specific date for now, but it will be around one month after 1.5.5 has been released. > > Below is my understanding, please let me know if I misunderstood something > here. > After 1.5.6, I need to version my pages (which is true by default) and also > setRecreateMountedPagesAfterExpiry(which is true by default). What wicket > does in the background is when session management fails or session expires, > instead of just throwing run time exception (like PageExpiredException) > wicket tries to reload the page (I am not sure how many times it retries > ??). By this way we may not or may get only small number of run time > exceptions. Am I right? Right. But only for pages mounted with #mountPage() (i.e. with MountedMapper) > > Sorry for too many questions because I didn't find any thread regarding page > version in latest releases. > > Thanks, > Suresh > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Version-Pages-by-default-tp4520432p4521893.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
