Setting and reading session attributes

Vaadin has a few different ways of storing data that should be accessible later. Which one you should use depends on the scope of the data, e.g. how long it should be kept around and what parts of the code should have access to it.

  1. Store the data as a field in your UI subclass. The data is easily accessible from components belonging to that UI instance and the data will be gone when the UI is closed.

  2. Store data in the VaadinServiceSession. The data is easily accessible from any UI belonging to the same VaadinServlet or VaadinPortlet and it will be gone when the session is closed.

  3. Store data in the HttpSession or PortletSession (represented in Vaadin through WrappedSession). The data is easily accessible from any part of your web application (i.e. your .war) and it will be gone when the session is invalidated.

The following example code demonstrates how the data is stored and retrieved in different ways.

Java

  1. //Remove comment to preserve UI value when reloading
  2. //@PreserveOnRefresh
  3. public class SettingReadingSessionAttributesUI extends UI {
  5.     private String value;
  7.     private VerticalLayout statusHolder = new VerticalLayout();
  8.     private TextField textField = new TextField();
  10.     @Override
  11.     protected void init(VaadinRequest request) {
  12.         addComponent(statusHolder);
  13.         addComponent(textField);
  14.         addComponent(new Button("Set new values", new Button.ClickListener() {
  15.             @Override
  16.             public void buttonClick(ClickEvent event) {
  17.                 String value = textField.getValue();
  19.                 saveValue(SettingReadingSessionAttributesUI.this, value);
  20.             }
  21.         }));
  22.         addComponent(new Button("Reload page", new Button.ClickListener() {
  23.             @Override
  24.             public void buttonClick(ClickEvent event) {
  25.                 getPage().setLocation(getPage().getLocation());
  26.             }
  27.         }));
  29.         showValue(this);
  30.     }
  32.     private static void saveValue(SettingReadingSessionAttributesUI ui,
  33.             String value) {
  34.         // Save to UI instance
  35.         ui.value = value;
  36.         // Save to VaadinServiceSession
  37.         ui.getSession().setAttribute("myValue", value);
  38.         // Save to HttpSession
  39.         VaadinService.getCurrentRequest().getWrappedSession()
  40.                 .setAttribute("myValue", value);
  42.         // Show new values
  43.         showValue(ui);
  44.     }
  46.     private static void showValue(SettingReadingSessionAttributesUI ui) {
  47.         ui.statusHolder.removeAllComponents();
  48.         ui.statusHolder.addComponent(new Label("Value in UI: " + ui.value));
  49.         ui.statusHolder.addComponent(new Label(
  50.                 "Value in VaadinServiceSession: "
  51.                         + ui.getSession().getAttribute("myValue")));
  52.         ui.statusHolder.addComponent(new Label("Value in HttpSession: "
  53.                 + VaadinService.getCurrentRequest().getWrappedSession()
  54.                         .getAttribute("myValue")));
  55.     }
  57. }

The UI stores and reads the value in three different ways. The UI instance value gets lost just by reloading the page as a new UI instance is then created unless the UI has been marked with @PreserveOnRefresh. If you deploy two different VaadinServlet instances using the same UI class, they will only share the HttpSession value.