Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

?restartApplication issue

aa bb
1 decade ago Sep 11, 2012 12:34pm
Thomas Mattsson
1 decade ago Sep 12, 2012 11:46am
aa bb
1 decade ago Sep 12, 2012 12:35pm
Thomas Mattsson
1 decade ago Sep 12, 2012 2:46pm
aa bb
1 decade ago Sep 12, 2012 4:16pm
Thomas Mattsson
1 decade ago Sep 13, 2012 1:55pm

No, that's not how Vaadin works; it tracks HTTP session with cookies, which typically aren't cleared alongside the cache. Clearing cookies would have the same effect as using restartApplication, except that the old session wouldn't be closed immediately.

The Vaadin application state is stored in the HTTP session on the server side, clearing the browser cache has no effect on this. As long as the browser can be identified (by the session cookie), it will be served the exact same application state that it had last time. This means the same exact Java Object of your Application class.

Roland Krüger
1 decade ago Sep 13, 2012 7:17pm

There's a cheaper option to enable an automatic redeployment of a Vaadin web application during development than using JRebel. This option is not as powerful as using JRebel, of course, but it works quite well nevertheless (and it's for free ;-) ). If you don't mind to use Maven as your build tool, you can follow the instructions described in my blog post at blog.oio.de to get an instant reloading of your Vaadin app while developing. You'll find an example Maven project on Github.

Last updated on Sep, 13th 2012
aa bb
1 decade ago Sep 17, 2012 3:55pm