Lombok

Hey, Tea Lovers! Java 16 is released a few days back, well, a month to be precise. It introduced 17 new features. I discussed the 4 features that the developer will use a lot in my previous post, Simplified Java 16 Key Features. In this post, we will deep dive into Java 16 Record to see how it helps us to reduce the boilerplate code of POJO classes. POJO Boilerplate Code Whenever you need a simple class to hold the data, you write a POJO class, right? But Even though your need is simple, you need to write tonnes of code for just a few things. Such as getters and setters, constructors, toString, and equals and hashcode. No matter how many different POJOs you write, you have to write these 90% similar methods. These things with little to no changes that we have to write again and again for simple purposes are known as Boilerplate code. ...

Hey, tea lovers! Ever wonder how Spring auto-wires the fields without using setters or constructors or Hibernate stores column values to the appropriate fields? or Gson converts your POJO to JSON? How are they reading the class’s field? and not only reading but changing or storing the values in them, even though they are private? Let me reveal the mystery. They are using Java Reflection API. What kind of magical substance is this? How these libraries are using them? How can we use them? Phew! too many questions to answer. Let’s just dive into it and find the answers. ...

Hey! Tea Lovers! We will discuss How to use Lombok in our code. It’s the continuation of our previous post " Say Good-Bye to Boilerplate Code with Lombok: Part 1-Installation". In which we looked at what Lombok is and how to install it in Eclipse or IntelliJ IDEA. Now, we will look at how we can use the Lombok library in our code. How to Use Lombok To use Lombok please be ready with the installation and dependencies which we discussed in the previous part. ...

Hey! Tea lovers! Before talking about Lombok, what are the things that irritate us Java Developers the most? Well yes, hearing “Java is dying” from a Python developer is irritating but it is the second thing. The first one is the boilerplate code. We write it almost every time. Setters and getters, constructors, toString, and many others for simple POJO classes. Of course, IDE can generate this code for you but again, your simple POJO class then becomes redundant. And the only things that matter in the POJO are the fields, so why not write fields only and let the compiler handles the rest of the things? And that’s where Project Lombok comes into the picture. ...