Skip to content
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

Force value coercion for java.util.Properties, so that values are Strings #810

Closed
cowtowncoder opened this issue May 28, 2015 · 0 comments
Closed
Milestone

Comments

@cowtowncoder
Copy link
Member

Currently there is no custom handling for java.util.Properties, and although it is possible to use it (since it really is a Map under the hood), results are only good if values are already Strings.
The problem here is that Properties is actually declared as Map<String,Object>, probably due to backwards-compatibility constraints.

But Jackson should know better: perhaps by TypeFactory tweaking parameterizations a bit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant