In Spring Web Flow the view is rendered first and then the conversation is updated in the session. We are using Resin for our web server. Resin stores the session in the database for clustering before the header is sent to the browser, so there is always one requested old session data in the database. Is it possible to configure Spring Web Flow to not render the view until the session information is updated?
Announcement Announcement Module
No announcement yet.