Tomcat not reloading Vaadin App’s View when running in Eclipse

Ever had the problem that changes to a Vaadin App’s UI were not reflected in the runtime when running and deploying to a Tomcat in Eclipse, even after reloading the app? Vaadin stores views in the Session, and a default Tomcat installation will use a persistent Session Manager. Sessions are recreated after the app has been reloaded when using the same browser with the same session key, and the stale view will be loaded from the session.

The solution is simple: In your context.xml (either in Tomcat’s conf dir, or in the Servers project in Eclipse), locate these lines and do what they say:

    <!-- Uncomment this to disable session persistence across Tomcat restarts -->
    <!--
    <Manager pathname="" />
    -->
About these ads
This entry was posted in Eclipse, Java, Vadiin. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s