Since Vaadin stores the session in memory, your application is not reset until it sees a new browser session (i.e., a cleared cache or a restarted browser). Another way to clear a session during development is to enable reloading of the application to your application URL. This will also clear the state of the application.
So, keeping in mind, itβs clear that if you like that the state of the Vaadin application is reset during normal use, you need to make sure programmatically that the internal logic works the way it is done. For instance. call the self-defined reset () method for your first view.
Make sure that you do not confuse this state of the session-based application with the state of the page that resets the application each time you click reload or reopen the link without creating a new browser session.
A section in Vaadin's book about this: http://vaadin.com/book/-/page/architecture.server-side.html
source share