Fortsätt till huvudinnehåll

Gradle and some notes on creating Java objects from JSON strings

This morning I spent my time commuting to work reading about a Test-Driven Development Stack for Java. Tools mentioned were Maven, Jetty, Mockito, and JAX-RS. I wanted to learn some more about Mockito so I spent some time reading on their website where I found out about this build automation system called Gradle that can be used instead of Maven. Interesting I thought, let's try it out.

So first things first. The Ubuntu repositories only contained a really old version of Gradle so I downloaded the binary distribution from the website. Installation consisted of the tricky task to decide where to extract the archive and set up my PATH to include the bin directory for Gradle.

Then I thought that I wanted a plugin for Eclipse so I can create Gradle projects and have some parts automatically generated. After searching the web for a short while I found Buildship that is a collection of Eclipse plug-ins that provide support for building software using Gradle.
The easiest way to install it in Eclipse is to use the Eclipse-Marketplace. A nice tutorial written by Lars Vogel can be found here.

 Now that I had a Gradle project in Eclipse it was finally time to pick up on the JSON in Java mini-project I started on yesterday. Adding Google's JSON Java library to the Gradle project was a piece of cake. Just add the line compile 'com.google.code.gson:gson:2.6.2' in the dependencies section of the build.gradle file and you are ready to go.

 Using the GsonBuilder makes it really pleasent to create Java objects from JSON strings. I created a simple User class with the private variables 'name' and 'age' and created new users by calling
User user = new GsonBuilder().create().gson.fromJson(jsonString, User.class);

 You Java developers are really spoiled with nice tools and cool libraries ;).

Kommentarer

Skicka en kommentar

Populära inlägg i den här bloggen

C# Enum as bit field

Bit field enum Whenever you wish to express combinations of properties of an object, bit fields are a good way to accomplish this. As a simple example, consider a file in the file system. It can be Readable , Writable , Hidden or a combination these. The different attributes can be defined as an enum : [Flags] public enum FileAttribute {   None      = 0b0000;   Readable  = 0b0001;   Writeable = 0b0010;   Hidden    = 0b0100; } To indicate that this enum is expected to be used as a bit field I have defined it with the FlagsAttribute . It is important to understand that the FlagsAttribute does nothing more than making some changes to how the ToString method of the enum works, making it possible to print out all flags. It does not introduce any validation or special treatment of the enum in any other way. I have defined the values of the different fields of the enum using binary representation, this should make it even more clear that this is a bit field and which bi
Skicka en kommentar
Läs mer

Codility tasks - Part I

I was recently faced with two codility tasks when applying for a job as an Embedded Software Engineer. For those of you who arn't familiar with Codility you can check out their website here:  www.codility.com Task one - Dominator The first task was called Dominator. The goal was to, given a std::vector of integers, find an integer that occurs in more than half of the positions in the vector. If no dominator was found -1 should be returned. My approach was to loop through the vector from the first to the last element, using a std::map to count the number of occurences of each integer. If the count ever reached above half the size of the vector I stopped and returned that integer and if I reached the end without finding a dominator I returned -1. So was that a good approach? Well, the reviewer at the company rated the solution as 'pretty ok'. His preferred solution was store the first integer in the array and set a counter to 1. Then loop through the remaining i
7 kommentarer
Läs mer