New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fluent Setters Not working with EnhancedClient #5039
Comments
@patrickjamesbarry as I mentioned in the documentation issue, I don't think fluent setters were in scope in the design. I'm changing this to a feature request to add support to fluent setters. |
@patrickjamesbarry discussed this with the rest of the team, and even though the v2 Enhanced Client bean doesn't support fluent setters like v1 Mapper, we'd like to keep to the standard bean concept. We'd like to know more about the impact of the lack of fluent setters in your use case. Is it for the coding experience? Or maybe you/your team don't have control over how the bean classes are created? Have you considered using Immutable classes? |
Looking through stackoverflow and github issues, you can see the oversight of this feature has burned many. So the initial submittal of this ticket was simply to formalize the request to patch this change. Why does the community want fluent setters? A quick google says it best: Jumping into your suggestion: A better alternative would be to support java record classes. https://www.baeldung.com/java-record-keyword |
Describe the bug
Our pojos/beans used with DynamoDbMapper (v1) used to work with fluent setters. This seems to be broken when using the EnhancedClient with v2.
Expected Behavior
expectation is that this bean would work (the name attribute would be set
Current Behavior
The attribute using a fluent setter does not work and the attribute will always be null
Reproduction Steps
Possible Solution
No response
Additional Information/Context
This has been reported in other tickets, but there has been no ticket created to fix or add this support.
example: #2213
AWS Java SDK version used
2.25.2
JDK version used
openjdk version "17.0.7" 2023-04-18
Operating System and version
mac 13.6.4
The text was updated successfully, but these errors were encountered: