Vaadin Application lifecycle and bundle lifetime don't match


When creating a Vaadin Application using the Vaadin-Application manifest entry the lifetime of the application and gets shared for all users. This is problematic for many applications and cause a feedback look between multiple browsers.

Suggest creating an ApplicationFactory so that these are created as needed by Vaadin.




Scott Parkerson
December 7, 2012, 10:30 PM
Matt Brozowski
December 19, 2012, 3:35 PM

Sorry to have missed the comments... For some reason I'm not getting email for these

The Application Lifecycle is NOT the same as that of the bundle. Every user that logs in gets his own instance of the application which is kept in the user's Session. The Application is destroyed with the Session is destroyed. Therefore the application lifecycle and the bundle lifecycle are not the same. If we share the same Application instance across users then user1 clicking a button gets called back in user2's Application instance causing very confused behavior.

I actually have a fix for this on a fork I made where I publish an ApplicationFactory as a service in my Vaadin bundle. Then this service creates the ApplicationServlet and uses the ApplicationFactory to create the Application object

Achim Nierbeck
February 7, 2013, 12:55 PM

Unfortunately nothing has been going on on this issue, so I'm gonna take over in the coming days.
I really want to get a first snapshot version out of the door and this one should be included

Achim Nierbeck
February 11, 2013, 11:05 AM

I did a first merge of both repositories in the PAXVAADIN-6 branch.
@Matt, btw. I've seen that there are a couple more new features in your branch, which I didn't merge. Do you want to share those also with pax-for-vaadin?

June 15, 2016, 3:06 AM


Matt Brozowski


Matt Brozowski



Fix versions

Affects versions