Description
It would be quite cool if you could define a bean with a lifecycle of "session" and Tapestry could take care of obtaining it from the session (as needed) and persisting it back to the session at the end of the requesty cycle, much like an application state object.