TOOLS on Flowing Code

Installing Vembu BDRSuite with Docker Compose

Mon, 11 Jul 2022 12:55:25 +0000

In these days we tend to think that just by having our services and data on the cloud everything related to backups is solved and is someone else problem. But for most of the companies this is not enough, and if we’re in charge of defining the infrastructure of an organization we should consider implementing several layers of backups no matter where the data is actually hosted.

Vaadin Widgetset compiling: Tips & Hints

Fri, 09 Feb 2018 19:36:00 +0000

Hi everyone!

The purpose of this post is enumerating the most common issues when trying to compile the widgetset in Vaadin. But before digging into this, let’s explain a little bit what this compiling thing is about.

In Vaadin version 6, 7 & 8, the visual components have two important parts.

The first one is server side, and it’s implemented in classic Java classes that are compiled to JVM bytecode.

The second part, on the other hand, is the client side code, written mostly in Java and then compiled in Javascript using GWT project. GWT is basically a Java to Javascript compiler. All of these components (widgets) belong to a set known as widgetset.

The widgetset compilation process is done by executing the GWT compiler to produce the Javascript code associated to all of the Vaadin components that have server and client side code.

That being said, let’s go on with those tips!

Verify that everything is correctly configured

There are a lot of ways to compile the widgetset, in this case we will focus in projects that use maven as the build tool, because is the most commonly tool used for this purpose.

The vaadin-maven-plugin will help you on this process, which is a derivation of the gwt-maven-plugin.

Depending on the Vaadin version used, there a are a lot of different configurations, the best thing to do, is to create a small maven project, based on the simplest vaadin maven archetype (com.vaadin:vaadin-archetype-application)

These are the steps for doing this:

Run the command “mvn archetype:generate” from a terminal or command line window
Enter “vaadin” to filter the list of the available archetypes
Choose 5 (currently that’s the number of the com.vaadin:vaadin-archetype-application archetype, it could change in the future)
Choose the number before the Vaadin version that you’re using (ie: 127 -> 7.7.13, etc.)
Complete the parameters that maven will prompt

After that, maven will generate a small project, and if you take a look to the pom.xml file that was generated, you are going to find something like this:

Debugging GWT client side code in Vaadin with Eclipse

Tue, 12 Dec 2017 14:17:00 +0000

You know, if you’re developing a Vaadin application, it is not necessary to understand how to code client side using GWT, unless you’re building your own custom component, and you need to add some special client-side code. In that case, you are going to realize that whenever you want to test your component, debugging it can be tricky.

The problem is that client side code is not executed by the JVM, instead that code is going to be executed by the browser, and because of this all of the debugging facilities provided by the Java platform are useless.

Let me tell you what you need to take into account for being able to successfully debug your code.

1 – Modify your .gwt.xml file

The first thing you need to do is to modify the file that contains all of your widgetset information, by adding this line inside the tag <module/>: