Paging for any content when you have too much data to display on the page: << < 1 2 3 ... > >>

You may have too much data to display on the page. For example, you have a search page and you only want to display the 20 first results. But the user must be able to browse the rest of the results. This add-on will very easily enable you to place numbers of pages to jump to.

You do not need to use a Table to use PagingComponent.

Examples are provided with a fake DAO, to simulate how you would retreive data for each page. You can also see the PagingComponentApplication class for more examples.

This is used in production in the platform, in the forum and the course search result page.


Link to this version
BetaReleased 26 August 2012Apache License 2.0
Framework Support
Vaadin 6.0+
Also supported:
Vaadin 7 (0.9.6)
Browser Independent
Install with
Release notes - Version 0.9.3
  • The style methods of PagingComponent become useless when a "Customizer" is given as parameter to the PagingComponent. In this case, these methods throw a RuntimeException to warn the programmer.

  • The methods for the creation of a separator in the ElementsCustomizer and the GlobalCustomizer return now a Component instead of a AbstractComponent.

  • PagingComponent have a new protected method called "createComponentsManager". You may override this method to use your own ComponentsManager.

  • Two new classes has been added. They allow to display the items more easily than the PagingComponentListener. So, you can use the SimplePagingComponentListener for eager loading and the LazyPagingComponentListener for lazy loading.