Skip to content

Allow use of "any setter" as a backup for Creator(-only) properties #1401

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.

Sign up for GitHub

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

Jump to bottom
Closed
cowtowncoder opened this issue Oct 5, 2016 · 1 comment
Closed

Allow use of "any setter" as a backup for Creator(-only) properties #1401

cowtowncoder opened this issue Oct 5, 2016 · 1 comment

Comments

@cowtowncoder
Copy link
Member

(note: evolution of #862)

In cases where Creator method is not used (via mapper.readerForUpdating(value), for example; in future possibly other mechanisms), it would be good to be able to re-route handling to any setter.
This is not easy to do, currently, but perhaps linkage is possible.
@cowtowncoder cowtowncoder mentioned this issue Oct 5, 2016
Closed
cowtowncoder added a commit that referenced this issue Oct 5, 2016
@cowtowncoder
add a (failing) test for #1401
df6ea43
cowtowncoder added a commit that referenced this issue Nov 9, 2016
@cowtowncoder
Minor improvement wrt #1401
bd9772f
@cowtowncoder cowtowncoder added 2.10 and removed 2.9 labels Sep 12, 2019
@cowtowncoder cowtowncoder removed the 2.10 label Apr 12, 2020
This was referenced Jan 27, 2024
Closed
Closed
@cowtowncoder
Copy link
Member Author

No plans to implement; closing as part of bigger issue clean up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cowtowncoder