Recommendation: Use Wrapper Types for POJO Fields and Avoid Default Values to Prevent Common Pitfalls
The article advises that POJO class attributes should always use wrapper types without preset default values, illustrating several pitfalls such as null‑overridden defaults during Jackson deserialization, BeanUtils copy failures, MyBatis dynamic SQL issues, and RPC/API default‑value bugs.
