Yes, we're now running our Black Friday Sale. All Access and Pro are 33% off until 2nd December, 2025:
Modern software architecture is often broken. Slow delivery leads to missed opportunities, innovation is stalled due to architectural complexities, and engineering resources are exceedingly expensive.
Orkes is the leading workflow orchestration platform built to enable teams to transform the way they develop, connect, and deploy applications, microservices, AI agents, and more.
With Orkes Conductor managed through Orkes Cloud, developers can focus on building mission critical applications without worrying about infrastructure maintenance to meet goals and, simply put, taking new products live faster and reducing total cost of ownership.
Try a 14-Day Free Trial of Orkes Conductor today.
Modern software architecture is often broken. Slow delivery leads to missed opportunities, innovation is stalled due to architectural complexities, and engineering resources are exceedingly expensive.
Orkes is the leading workflow orchestration platform built to enable teams to transform the way they develop, connect, and deploy applications, microservices, AI agents, and more.
With Orkes Conductor managed through Orkes Cloud, developers can focus on building mission critical applications without worrying about infrastructure maintenance to meet goals and, simply put, taking new products live faster and reducing total cost of ownership.
Try a 14-Day Free Trial of Orkes Conductor today.
Mocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.
Get started with mocking and improve your application tests using our Mockito guide:
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.
But these can also be overused and fall into some common pitfalls.
To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:
Explore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:
Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.
I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.
You can explore the course here:
Modern software architecture is often broken. Slow delivery leads to missed opportunities, innovation is stalled due to architectural complexities, and engineering resources are exceedingly expensive.
Orkes is the leading workflow orchestration platform built to enable teams to transform the way they develop, connect, and deploy applications, microservices, AI agents, and more.
With Orkes Conductor managed through Orkes Cloud, developers can focus on building mission critical applications without worrying about infrastructure maintenance to meet goals and, simply put, taking new products live faster and reducing total cost of ownership.
Try a 14-Day Free Trial of Orkes Conductor today.
Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.
Get started with Spring Data JPA through the guided reference course:
Refactor Java code safely — and automatically — with OpenRewrite.
Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.
Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.
Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.
Regression testing is an important step in the release process, to ensure that new code doesn't break the existing functionality. As the codebase evolves, we want to run these tests frequently to help catch any issues early on.
The best way to ensure these tests run frequently on an automated basis is, of course, to include them in the CI/CD pipeline. This way, the regression tests will execute automatically whenever we commit code to the repository.
In this tutorial, we'll see how to create regression tests using Selenium, and then include them in our pipeline using GitHub Actions:, to be run on the LambdaTest cloud grid:
Yes, we're now running our Black Friday Sale. All Access and Pro are 33% off until 2nd December, 2025:
1. Overview
Sometimes, we want to hide the ability to get or set a field value in our objects. But Lombok generates the default getter/setter automatically. In this quick tutorial, we’ll show how we can omit the getters and setters from being generated by Lombok. A detailed look at the Project Lombok library is also available in Introduction to Project Lombok.
Before continuing, we should install the Lombok plugin in our IDE.
2. Dependencies
First, we need to add Lombok to our pom.xml file:
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.30</version>
<scope>provided</scope>
</dependency>3. Default Behavior
Before we get into the details of how to omit the generation of getters and setters, let’s review the default behavior of the annotations responsible for generating them.
3.1. @Getter and @Setter Annotations
Lombok provides two accessor annotations, @Getter and @Setter. We can annotate every field or simply mark the whole class with them. Generated methods will be public by default. However, we can change the access level to protected, package, or private. Let’s see an example:
@Setter
@Getter
public class User {
private long id;
private String login;
private int age;
}We can use the delombok option from the plugin in our IDE and see the code Lombok generated:
public class User {
private long id;
private String login;
private int age;
public long getId() {
return this.id;
}
public String getLogin() {
return this.login;
}
public int getAge() {
return this.age;
}
public void setId(long id) {
this.id = id;
}
public void setLogin(String login) {
this.login = login;
}
public void setAge(int age) {
this.age = age;
}
}As we can observe, all getters and setters were created. Getter and setters for all fields are public because we didn’t specify the access level on any field explicitly.
3.2. @Data Annotation
@Data combines features of a few other annotations, including both @Getter and @Setter. So, in this case, default accessor methods will be generated as public also:
@Data
public class Employee {
private String name;
private String workplace;
private int workLength;
}4. Omitting Getter or Setter Using AccessLevel.NONE
To disable default getter/setter generation on a specific field, we should use a specific access level:
@Getter(AccessLevel.NONE)
@Setter(AccessLevel.NONE)This access level lets us override the behavior of a @Getter, @Setter, or @Data annotation on a class. To override the access level, annotate the field or class with an explicit @Setter or @Getter annotation.
4.1. Overriding @Getter and @Setter Annotations
Let’s change the AccessLevel to NONE on the getter for the age field and the setter for the id field:
@Getter
@Setter
public class User {
@Setter(AccessLevel.NONE)
private long id;
private String login;
@Getter(AccessLevel.NONE)
private int age;
}Let’s delombok this code:
public class User {
private long id;
private String login;
private int age;
public long getId() {
return this.id;
}
public String getLogin() {
return this.login;
}
public void setLogin(String login) {
this.login = login;
}
public void setAge(int age) {
this.age = age;
}
}As we can see, there’s no setter for the id field and go getter for the age field.
4.2. Overriding the @Data Annotation
Let’s see another example, in which we change the AccessLevel to NONE on the class with the @Data annotation:
@Data
public class Employee {
@Setter(AccessLevel.NONE)
private String name;
private String workplace;
@Getter(AccessLevel.NONE)
private int workLength;
}We added the explicit @Getter annotation to the workLength field and explicit @Setter annotation to the name field. The AccessLevel of both accessors is set to NONE. Let’s see the delombok code:
public class Employee {
private String name;
private String workplace;
private int workLength;
public String getName() {
return this.name;
}
public String getWorkplace() {
return this.workplace;
}
public void setWorkplace(String workplace) {
this.workplace = workplace;
}
public void setWorkLength(int workLength) {
this.workLength = workLength;
}
}As we expected, our explicit settings of @Getter and @Setter override the getters and setters generated by the @Data annotation. There is no setter generated for the name field and no getter generated for the workLength field.
5. Conclusion
In this article, we explored how to omit getter and setter generation by Lombok for specific fields in our objects. Moreover, we saw examples for @Getter, @Setter, and @Data annotations. Next, we saw the code that Lombok generated for our annotation settings.
The code backing this article is available on GitHub. Once you're logged in as a Baeldung Pro Member, start learning and coding on the project.
