Filter
Exclude
Time range
-
Near
Circular MapStruct mapping between Customer and NextOfKin? Stack overflow. Infinite loop. Obvious in hindsight. But it's a reminder: your mapper reflects your domain model. If your domain has circular references, your mapping layer will expose them without mercy.
1
21
The others? I've been here before. Ambiguous @ExceptionHandler. LazyInitializationException. StackOverflow from circular MapStruct mappings. Not new. Not surprising. But a financial system has a way of sharpening why these things matter.
1
1
Falta só implementar os UseCase de Review, e os métodos de update que eu vou usar mapStruct eu acho, já fiz boa parte do que faltava,já testei e gostei bastante do resultado inicial.
18
564
🎯 Master null handling in MapStruct and simplify your Java mapping layer.
1
3
859
🧠 MapStruct helps teams standardize object mapping behavior across applications.
3
959
🧩 Partial updates become much easier with the right MapStruct configuration.
2
553
☕ Null handling in Java mappings can get messy fast. MapStruct makes it cleaner.
2
968
Replying to @abolorreeeee
Does Go have any library for DTO-domain/entity mapping? In Springboot we have Mapstruct or we build manually using @Builder annotation on the domain/entity, depending on the use case.
2
3
129
Do you need to write a lot of mapping code in order to map between different object models? MapStruct simplifies this task by generating the code. In this blog, you will learn some basic features of MapStruct. #java mydeveloperplanet.com/2024/0…
13
760
The Java pattern every backend developer should know in 2026: Record Builder for immutable DTOs: In real-world Java projects (Spring Boot APIs, microservices, event systems, data pipelines), we create dozens of DTOs every week. The best modern pattern: Records (immutable by default) Builder pattern for flexible construction while keeping immutability. Benefits: - Immutable → thread-safe and predictable No boilerplate getters/setters Builder gives nice fluent API for optional fields Excellent integration with Jackson, MapStruct, validation, etc. Realistic production example below:
1
7
64
11,839
The most practical Java pattern used in real production systems: Record Builder for immutable DTOs: In real-world Java projects (Spring Boot APIs, microservices, event-driven systems, data pipelines), we create dozens of DTOs every week for requests, responses, events, and projections. The best modern pattern in 2026: Records (immutable by default) Builder pattern for flexible construction while keeping immutability. Benefits: - Immutable → thread-safe and predictable - No boilerplate getters/setters - Builder gives nice fluent API for optional fields - Works perfectly with Jackson, MapStruct, validation, etc. Realistic production example below:
2
5
30
803
One of the most valuable Java patterns in production: Immutable DTOs with Records Builder: In real-world Java applications (Spring Boot APIs, microservices, event systems), we create hundreds of DTOs. The best modern pattern in 2026: Records (immutable by default) Builder pattern for flexible construction.Benefits:Immutable → thread-safe and predictable No boilerplate getters/setters Builder gives nice fluent API for optional fields Excellent integration with Jackson, validation, and MapStruct Realistic production example below:
3
11
67
4,083
One of the most practical Java patterns used in real production systems: Record as immutable DTO with validation: In real-world Java applications (Spring Boot APIs, microservices, event-driven systems), we create dozens of DTOs every week. The best modern approach in 2026: Use records for immutable DTOs Jakarta Bean Validation for clean validation. Benefits: - Immutable by default → thread-safe & predictable - No boilerplate getters/setters - Validation is declarative and reusable - Works perfectly with Jackson, MapStruct, and controllers Realistic example below:
2
6
61
2,000
The most practical Java pattern every backend developer should use in 2026: Record Builder pattern for immutable DTOs: In real-world Java projects (Spring Boot, microservices, APIs, data pipelines), we constantly create DTOs for requests, responses, events, and database projections. The best modern pattern:Use records (immutable by default) Builder pattern for flexible construction while keeping immutability. Benefits: - Immutable → thread-safe & predictable - No boilerplate getters/setters - Builder gives nice fluent API for optional fields - Works perfectly with Jackson, MapStruct, validation, etc. Realistic example below:
8
15
177
24,094
MapStruct Quarkus works… until you hit native builds or dev mode. Then the fun begins: • ClassNotFoundException • Stale mappers • Hot-reload confusion The Quarkiverse MapStruct extension fixes all of it — cleanly. buff.ly/ombXitp #Java #Quarkus #GraalVM
3
13
661
Do you need to write a lot of mapping code in order to map between different object models? MapStruct simplifies this task by generating the code. In this blog, you will learn some basic features of MapStruct. #java mydeveloperplanet.com/2024/0…
7
413
¿Sigues mapeando objetos a mano en Java? 😮 Eso es como usar papel carbón en plena era digital. Usa MapStruct y dile adiós al boilerplate. ➡️ Más rápido ➡️ Más limpio ➡️ Menos bugs #Java #MapStruct #CleanCode #DevLife 🧰🚀
1
3
27
1,123