Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Vaadin 7 UI Design By Example: Beginner's Guide

You're reading from   Vaadin 7 UI Design By Example: Beginner's Guide Do it all with Java! All you need is Vaadin and this book which shows you how to develop web applications in a totally hands-on approach. By the end of it you'll have acquired the knack and taken a fun journey on the way.

Arrow left icon
Product type Paperback
Published in Jul 2013
Publisher Packt
ISBN-13 9781782162261
Length 246 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Toc

Table of Contents (17) Chapters Close

Vaadin 7 UI Design By Example Beginner's Guide
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
1. Writing Your First Vaadin-powered Application FREE CHAPTER 2. Using Input Components and Forms – Time to Listen to Users 3. Arranging Components into Layouts 4. Using Vaadin Navigation Capabilities 5. Using Tables – Time to Talk to Users 6. Adding More Components 7. Customizing UI Components – Time to Theme it 8. Developing Your Own Components Pop Quiz Answers Index

User session


A user session is like a place that Java web applications use to store data about each user. Each time a user access the application, a new session object is assigned to it. That means that each user has its own session. A session allows us to identify a user. It is a temporal storage where we (and Vaadin) can put data relevant to a user.

Note

Because sessions are temporal, we can configure their lifetime (or timeout) in web.xml:

<web-app ...>
   ...
  <session-config>
    <session-timeout>20</session-timeout>
  </session-config>
</web-app>

Note

Here, each session will last 20 minutes since the last time the user requested something to the server.

Vaadin automatically preserves the state of UI components (if @preserveOnRefresh is present) by storing the required UI data into the user session. We don't have to worry about preserving UI components state. However we can still use the user session to store stuff not covered by any UI component. For...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime