-
Notifications
You must be signed in to change notification settings - Fork 115
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
Cannot add a custom writer for an interface #12
Comments
I see a couple of issues with what is listed here. First, the field type Second, overriding CharSequence is asking for trouble, as that would also On Mon, Jul 7, 2014 at 6:20 PM, LXE notifications@github.com wrote:
|
|
To summarize, if the object graph is
I want to ensure the following postcondition:
no matter what the concrete type of data was before calling javaToJson(originalPojo). |
So far I went without it by doing the conversion (.toString()) in the field setter - but that's not as efficient as it could be (the setter could have been called many times before the actual serialization). |
Use case:
Expected:
Actual:
P.S. For interfaces, I'd also appreciate the ability to stick to a default implementation explicitly (i.e. override the concrete type upon deserialization - of course, within types assignable to the declared field type).
The text was updated successfully, but these errors were encountered: