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
Regression: custom serializers broken again #34
Comments
RuedigerMoeller
added a commit
that referenced
this issue
Oct 19, 2014
RuedigerMoeller
added a commit
that referenced
this issue
Oct 19, 2014
RuedigerMoeller
added a commit
that referenced
this issue
Oct 19, 2014
fixed with 2.09. mvn upload underway (~6-12 hours until available). Thanks for report + testcase :-) |
RuedigerMoeller
added a commit
that referenced
this issue
Oct 19, 2014
Thanks for the quick fix. :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#2 is back, tested with 2.08. Test case available at http://pastebin.com/NYmJiu4s
It works if the setForceSerializable line is uncommented, and the custom serializer does get invoked in that case. But the documentation doesn't say you need setForceSerializable to use custom serializers, and that would result in unwanted behavior for other non-serializable classes that don't have custom serializers registered.
The text was updated successfully, but these errors were encountered: