This program creates a Person object and uses Jackson's ObjectMapper to convert it to a nicely formatted JSON string. It then prints the JSON.
Spring Boot
import com.fasterxml.jackson.databind.ObjectMapper;
import com.fasterxml.jackson.databind.SerializationFeature;
import java.util.List;
public class JsonExample {
public static class Person {
public String name;
public int age;
public Person(String name, int age) {
this.name = name;
this.age = age;
}
}
public static void main(String[] args) throws Exception {
Person person = new Person("John", 28);
ObjectMapper mapper = new ObjectMapper();
mapper.enable(SerializationFeature.INDENT_OUTPUT);
String json = mapper.writeValueAsString(person);
System.out.println(json);
}
}
OutputSuccess
Important Notes
Jackson uses public fields or getters to find data to serialize.
You can customize JSON output with annotations like @JsonProperty or by configuring ObjectMapper.
Remember to handle exceptions because serialization can fail if objects are not compatible.
Summary
Jackson converts Java objects to JSON strings easily.
Use ObjectMapper and writeValueAsString() for serialization.
Enable pretty print with SerializationFeature for readable JSON output.
Practice
(1/5)
1. What is the primary purpose of Jackson in a Spring Boot application?
easy
A. To convert Java objects to JSON and vice versa
B. To manage database connections
C. To handle HTTP requests
D. To style HTML pages
Solution
Step 1: Understand Jackson's role
Jackson is a library used to convert Java objects into JSON format and back.
Step 2: Compare options with Jackson's function
Only To convert Java objects to JSON and vice versa describes this conversion role; others relate to different tasks.
Final Answer:
To convert Java objects to JSON and vice versa -> Option A
Quick Check:
Jackson = Java-JSON conversion [OK]
Hint: Jackson is for JSON conversion, not database or UI tasks [OK]
Common Mistakes:
Confusing Jackson with database or HTTP handling
Thinking Jackson styles HTML
Assuming Jackson manages server requests
2. Which of the following is the correct way to serialize a Java object to a JSON string using Jackson's ObjectMapper?
easy
A. objectMapper.readValue(object, String.class);
B. objectMapper.writeValueAsString(object);
C. objectMapper.toJson(object);
D. objectMapper.serialize(object);
Solution
Step 1: Identify the serialization method in ObjectMapper
The method to convert an object to JSON string is writeValueAsString.
Step 2: Check other options for correctness
readValue is for deserialization, toJson and serialize are not valid ObjectMapper methods.
Final Answer:
objectMapper.writeValueAsString(object); -> Option B
Quick Check:
Serialize with writeValueAsString() [OK]
Hint: Use writeValueAsString() to convert object to JSON string [OK]
Common Mistakes:
Using readValue() instead of writeValueAsString()
Assuming toJson() or serialize() exist in ObjectMapper
Mixing serialization and deserialization methods
3. Given the following code snippet, what will be the output?
ObjectMapper mapper = new ObjectMapper();
User user = new User("Alice", 30);
String json = mapper.writeValueAsString(user);
System.out.println(json);
Assuming User class has fields 'name' and 'age' with getters.
medium
A. {"Alice":30}
B. {"userName":"Alice","userAge":30}
C. {"name":"Alice","age":30}
D. Error: Cannot serialize User object
Solution
Step 1: Understand default serialization of User object
Jackson serializes fields with their names and values, so 'name' and 'age' become JSON keys and values.
Step 2: Match output with expected JSON format
{"name":"Alice","age":30} matches the expected JSON string with keys 'name' and 'age' and their values.
Final Answer:
{"name":"Alice","age":30} -> Option C
Quick Check:
Default serialization = field names as keys [OK]
Hint: Default JSON keys match Java field names with getters [OK]
Common Mistakes:
Expecting custom key names without annotations
Assuming serialization fails without extra config
Confusing field names with variable names
4. What is wrong with this code snippet that tries to pretty-print JSON?
ObjectMapper mapper = new ObjectMapper();
mapper.enable(SerializationFeature.PRETTY_PRINT);
String json = mapper.writeValueAsString(user);
medium
A. SerializationFeature.PRETTY_PRINT does not exist; should use INDENT_OUTPUT
B. writeValueAsString cannot produce pretty JSON
C. ObjectMapper must be configured with a custom serializer
D. Pretty print requires calling writeValue() instead
Solution
Step 1: Check correct SerializationFeature for pretty print
The correct feature name is INDENT_OUTPUT, not PRETTY_PRINT.
Step 2: Verify usage of writeValueAsString
writeValueAsString supports pretty printing if INDENT_OUTPUT is enabled.
Final Answer:
SerializationFeature.PRETTY_PRINT does not exist; should use INDENT_OUTPUT -> Option A
Quick Check:
Use INDENT_OUTPUT for pretty print [OK]
Hint: Use SerializationFeature.INDENT_OUTPUT for pretty JSON [OK]
Common Mistakes:
Using wrong feature name PRETTY_PRINT
Thinking writeValueAsString can't pretty print
Believing custom serializers are always needed
5. You want to serialize a Java object to JSON but exclude null fields from the output. Which Jackson configuration achieves this?
hard
A. mapper.setSerializationInclusion(JsonInclude.Include.ALWAYS);
B. mapper.disable(SerializationFeature.WRITE_NULLS);
C. mapper.enable(SerializationFeature.EXCLUDE_NULLS);
D. mapper.setSerializationInclusion(JsonInclude.Include.NON_NULL);
Solution
Step 1: Identify correct method to exclude null fields
Jackson uses setSerializationInclusion with JsonInclude.Include.NON_NULL to skip nulls.
Step 2: Check other options for validity
WRITE_NULLS and EXCLUDE_NULLS are not valid features; ALWAYS includes all fields.
Final Answer:
mapper.setSerializationInclusion(JsonInclude.Include.NON_NULL); -> Option D
Quick Check:
Exclude nulls with NON_NULL inclusion [OK]
Hint: Use NON_NULL inclusion to skip null fields [OK]
Common Mistakes:
Using non-existent SerializationFeature flags
Confusing ALWAYS with excluding nulls
Trying to disable null writing with wrong methods
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.