I think there is a problem with Tapestry-2.2-alpha-4 and stale sessions.
I was working on a web app which had persistent page state to determine the current page displayed and the number of items to show on the page (similar to WODisplayGroup). This worked fine under alpha-3 but when I moved to alpha-4 I couldn't page forward or back without Tapestry throwing a stale session error. I have read the section about stale session exceptions on the home page, but a session had already been created. Reverting back to alpha-3 stopped the exceptions. The log file didn't show anything unusual. If I can give you any further detail I'd be happy to.
Regards,
Simon
