-
-
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#canSerialize(Object.class) returns false even though FAIL_ON_EMPTY_BEANS is disabled #978
Milestone
Comments
flexfrank
added a commit
to flexfrank/jackson-databind
that referenced
this issue
Oct 21, 2015
flexfrank
added a commit
to flexfrank/jackson-databind
that referenced
this issue
Oct 21, 2015
Did you run full unit test suite with both possible fixes? It would seem like changes could have side effects. |
I ran
|
Closed
Looks like there is bit of prior art wrt #703. But I think that mostly refers to case of "fail on empty" being true, whereas this is for it being false. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: 2.5.x, 2.6.x
When
FAIL_ON_EMPTY_BEANS
is disabled,ObjectMapper#writeValueAsString(new Object())
succeeds.However,
ObjectMapper#canSerialize(Object.class)
returns false.I suppose 152aabb caused this problem.
The text was updated successfully, but these errors were encountered: