Introduction

This chapter will discuss testing, recompilation of widgetsets, auto-reloading changes on classpath in Maven, and will give a tip on how to handle uncatched exceptions in the production mode.

Simply put, day-to-day coding in Vaadin consists of working in Java source code, recompilation of the source codes, and refreshing the browser so that we can see the result of our work. Let's have a look at each activity separately.

Because Vaadin's application code is written in an object-oriented programming (OOP) language, such as Java, we can easily create cool object structures following OOP principles (basically encapsulation, inheritance, and abstraction).

The most important stuff to keep in mind is to define clear responsibilities for our Vaadin project components. Therefore we keep our application components separated from each other so that they can become easily testable (a component is represented by a class or a set of classes). Doing this, we will be well on our way to making...