Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Obtaining Request Data in Vaadin 7

DZone's Guide to

Obtaining Request Data in Vaadin 7

· Java Zone ·
Free Resource

Build vs Buy a Data Quality Solution: Which is Best for You? Gain insights on a hybrid approach. Download white paper now!

I confess, Vaadin 6 was good, but Vaadin 7 is even better. This article will detail most nastiness that is managed by this new version so that we only have to code a few lines to achieve our goals. One of such goal is the search of information about the request and the client.

In Vaadin 6, it was possible, but cumbersome for we had to force our application to implement the HttpServletRequestListener interface. The interface let us access the servlet request (as well as the servlet response), and then we were on our own.

In Vaadin 7, the Vaadin team identified recurring needs to some piece of data and provided a Vaadin API to access them easily; for example:

  1. The user agent type and its version (major and minor)
  2. The user's locale to initialize resources bundles
  3. The screen size, as well as the underlying viewpoint size to adapt the layour to the available space
  4. The URL fragment (#) to restore data

Vaadin 7 Root's init() method takes a WrapperRequest as a parameter, that is the entry point into these informations. Behold how we could address the above needs:

public class Vaadin7Root extends Root {
 
    @Override
    public void init(WrappedRequest wrapped) {
 
        BrowserDetails details = wrapped.getBrowserDetails();
 
        WebBrowser browser = details.getWebBrowser();
 
        // Need #1
        browser.getBrowserApplication();    // User agent
        browser.getBrowserMajorVersion();   // Major version
        abrowser.getBrowserMinorVersion();  // Minor version
 
        // Need #2
        browser.getLocale();                // User locale
         
        // Need #3
        browser.getClientHeight();          // Browser height
        browser.getClientWidth();           // Browser width
        browser.getScreenHeight();          // Viewpoint height
        browser.getScreenWidth();           // Viewpoint width
 
        // Need #4
        details.getUriFragment());          // URI fragment
    }

 No more dirty plumbing into the ServletRequest, welcome to a world of easy reading!

The ready-to-use WAR file is available here (sources included).

Note: There's a large difference in behavior between version 6 and 7 of Vaadin. In Vaadin 7, refreshing the browser will cause the init() method to be called again. 

Build vs Buy a Data Quality Solution: Which is Best for You? Maintaining high quality data is essential for operational efficiency, meaningful analytics and good long-term customer relationships. But, when dealing with multiple sources of data, data quality becomes complex, so you need to know when you should build a custom data quality tools effort over canned solutions. Download our whitepaper for more insights into a hybrid approach.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}