dexchong opened a new issue, #15805: URL: https://github.com/apache/dubbo/issues/15805
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Dubbo Version Dubbo 3.3.5 + JDK 17+Hession2 Dubbo 3.1.11 + JDK 17+Hession2 ### Steps to reproduce this issue When consumers send requests with the v1 entity class (without the addTime field): the Dubbo 3.1.11 provider (using the v2 entity class) obtains the default time, but the 3.3.5 version gets null. It is expected that when the consumer does not pass addTime, the 3.3.5 provider will automatically retrieve the default value from the v2 entity class. ``` //provider v1 @Data public class BatchGetOrderInfoParams implements Serializable { } //provider v2 @Data public class BatchGetOrderInfoParams implements Serializable { //default date value new Date(System.currentTimeMillis()); private Date addTime=new Date(System.currentTimeMillis()); } ``` <img width="900" height="107" alt="Image" src="https://github.com/user-attachments/assets/1c17ee60-d104-4c25-8fc1-d30dfd9e0f0e"; /> <img width="2166" height="260" alt="Image" src="https://github.com/user-attachments/assets/8e7d1c62-06be-4728-b457-9254831eb8e4"; /> ### What you expected to happen Ensure that the Hessian2 serialization of Dubbo 3.1.11 and 3.3.5 providers behaves consistently when handling default values of newly added fields, and the 3.3.5 provider automatically retrieves the default value from the v2 entity class. ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [x] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
