-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
ObjectMapper.writerWithType has no effect in 2.3.0 #412
Comments
It sounds like this could well be a be a bug. But I am not sure I follow the exact problem, so it would be great if you could come up with a simple unit test. And hopefully fix the problem. |
Sure - Here's a simple failing test:
The actual result is |
cowtowncoder
added a commit
that referenced
this issue
Feb 26, 2014
cowtowncoder
added a commit
that referenced
this issue
Feb 26, 2014
cowtowncoder
added a commit
that referenced
this issue
Feb 26, 2014
Fixed; was simply not using root type for locating root name to use. Will be in 2.3.2 (and 2.4) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using
ObjectMapper.writerWithType
on an ObjectMapper that hasSerializationFeature.WRAP_ROOT_VALUE
enabled to override the rootType when writing a value as a string. Specifically I'm doing this to ensure that proxied types have their parent class name written instead of the proxy class name.This worked fine with 2.1.1. Did something change?
The text was updated successfully, but these errors were encountered: