Entity to DTO mapping in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of mapping an Entity to a DTO in Spring Boot?

Mapping an Entity to a DTO helps separate the database model from the data sent over the network. It keeps the API clean and secure by exposing only needed data.

beginner

Which annotation is commonly used to mark a class as an Entity in Spring Boot?

The @Entity annotation marks a class as a database entity in Spring Boot.

beginner

What is a DTO and why is it useful?

DTO stands for Data Transfer Object. It is a simple object used to carry data between processes, often to avoid exposing the full Entity and to optimize data sent to clients.

intermediate

Name one popular library used in Spring Boot to automate Entity to DTO mapping.

MapStruct is a popular library that automatically generates code to map between Entities and DTOs in Spring Boot.

intermediate

What is a common manual way to convert an Entity to a DTO in Spring Boot?

A common manual way is to create a constructor or static method in the DTO class that takes an Entity object and copies the needed fields.

Why should you use a DTO instead of returning an Entity directly in a Spring Boot REST API?

A To hide sensitive data and control what is exposed

B Because Entities cannot be serialized

C To make the API slower

D Because DTOs are required by Spring Boot

DTOs help control what data is sent to clients, hiding sensitive or unnecessary fields.

Which annotation marks a class as a database Entity in Spring Boot?

A @Service

B @Repository

C @Controller

D @Entity

@Entity tells Spring Boot this class maps to a database table.

What does MapStruct do in the context of Entity to DTO mapping?

A Generates mapping code automatically

B Creates database tables

C Handles HTTP requests

D Manages application security

MapStruct generates code to convert Entities to DTOs and vice versa.

Which of these is NOT a reason to use DTOs?

A Improve API security

B Reduce data sent over network

C Directly expose database schema

D Simplify client data handling

DTOs help avoid exposing the database schema directly.

How can you manually map an Entity to a DTO?

A By calling the database directly from DTO

B By writing a method that copies fields from Entity to DTO

C By using @Entity annotation on DTO

D By using @RestController on Entity

Manual mapping involves copying needed fields from the Entity to the DTO.

Explain why and how you would map an Entity to a DTO in a Spring Boot application.

Think about what data you want to share with users and how to keep your database safe.

Describe a simple manual approach to convert an Entity object to a DTO object in Spring Boot.

Imagine packing only the things you want to send in a box.

Practice

1. What is the main purpose of mapping an Entity to a DTO in Spring Boot?

easy

A. To speed up database queries

B. To separate database structure from data sent to clients

C. To store data in a different database

D. To automatically generate database tables

Solution

1. Step 1: Understand Entity and DTO roles

   Entity represents database data, DTO is for data transfer outside the app.

2. Step 2: Identify the purpose of mapping

   Mapping hides database details and controls what data is sent to clients.

3. Final Answer:

   To separate database structure from data sent to clients -> Option B

4. Quick Check:

   Entity to DTO mapping = data separation [OK]

Hint: Think: Entity is internal, DTO is external data format [OK]

Common Mistakes:

• Confusing DTO with database storage
• Thinking mapping speeds up queries
• Assuming DTO changes database schema

2. Which of the following is the correct way to manually map an Entity field name to a DTO field fullName in Java?

easy

A. entity.getName(dto.setFullName());

B. entity.setName(dto.getFullName());

C. dto.getFullName(entity.setName());

D. dto.setFullName(entity.getName());

Solution

1. Step 1: Identify source and target objects

   Entity is source, DTO is target for mapping.

2. Step 2: Use getter on entity and setter on DTO

   Correct syntax is calling entity.getName() and passing to dto.setFullName().

3. Final Answer:

   dto.setFullName(entity.getName()); -> Option D

4. Quick Check:

   Getter from entity, setter on DTO [OK]

Hint: Getter from entity, setter on DTO for mapping [OK]

Common Mistakes:

• Reversing source and target in mapping
• Using setter as getter or vice versa
• Calling methods with wrong parameters

3. Given the following code snippet, what will be the output of dto.getAge() after mapping?

public class UserEntity {
  private int age = 30;
  public int getAge() { return age; }
}

public class UserDTO {
  private int age;
  public void setAge(int age) { this.age = age; }
  public int getAge() { return age; }
}

UserEntity entity = new UserEntity();
UserDTO dto = new UserDTO();
dto.setAge(entity.getAge());
System.out.println(dto.getAge());

medium

A. 30

B. 0

C. null

D. Compilation error

Solution

1. Step 1: Check initial value in Entity

   Entity's age is set to 30 by default.

2. Step 2: Map Entity age to DTO and print

   DTO's age is set to entity.getAge(), so dto.getAge() returns 30.

3. Final Answer:

   30 -> Option A

4. Quick Check:

   Entity age 30 mapped to DTO age 30 [OK]

Hint: Mapping copies values exactly unless changed [OK]

Common Mistakes:

• Assuming default int is null
• Confusing getter/setter roles
• Expecting compilation error without syntax issues

4. Identify the error in this manual mapping method:

public UserDTO mapToDTO(UserEntity entity) {
  UserDTO dto = new UserDTO();
  dto.setName(entity.getFullName());
  dto.setEmail(entity.getEmail());
  return dto;
}

Assuming UserEntity has a getName() method but no getFullName() method.

medium

A. Setter methods used incorrectly

B. Missing return statement

C. Calling non-existent method getFullName() on entity

D. DTO object not created

Solution

1. Step 1: Check entity methods used

   Code calls entity.getFullName(), but entity only has getName().

2. Step 2: Identify cause of error

   Calling a method that does not exist causes a compile-time error.

3. Final Answer:

   Calling non-existent method getFullName() on entity -> Option C

4. Quick Check:

   Method must exist on entity for mapping [OK]

Hint: Verify entity methods before calling in mapping [OK]

Common Mistakes:

• Assuming method names match automatically
• Ignoring compile errors from wrong method calls
• Confusing getter names between classes

5. You want to map a list of UserEntity objects to a list of UserDTO objects using Java streams in Spring Boot. Which code snippet correctly performs this mapping assuming a method mapToDTO(UserEntity entity) exists?

hard

A. List<UserDTO> dtos = entities.stream().map(this::mapToDTO).collect(Collectors.toList());

B. List<UserDTO> dtos = entities.map(entity -> mapToDTO(entity));

C. List<UserDTO> dtos = entities.forEach(entity -> mapToDTO(entity));

D. List<UserDTO> dtos = entities.stream().forEach(this::mapToDTO);

Solution

1. Step 1: Use stream() to process list

   entities.stream() creates a stream to transform elements.

2. Step 2: Use map() to convert each entity to DTO

   map(this::mapToDTO) applies the mapping method to each element.

3. Step 3: Collect results into a list

   collect(Collectors.toList()) gathers mapped DTOs into a list.

4. Final Answer:

   List<UserDTO> dtos = entities.stream().map(this::mapToDTO).collect(Collectors.toList()); -> Option A

5. Quick Check:

   Stream map + collect to list = correct mapping [OK]

Hint: Use stream().map(...).collect(toList()) for list mapping [OK]

Common Mistakes:

• Using forEach instead of map for transformation
• Calling map on list directly without stream()
• Not collecting results after mapping