On Wed, Aug 15, 2018 at 7:08 AM, Lyubomyr Shaydariv
wrote:
> Oh, I realized it... Yes, you are totally right and I missed that the whole
> point that the purpose of JsonDeserializer is returning an
> already-deserialized object. But for some reason I mixed it up with what
> should create an
Oh, I realized it... Yes, you are totally right and I missed that the whole
point that the purpose of JsonDeserializer is returning an
already-deserialized object. But for some reason I mixed it up with what
should create an instance (i.e. `InstanceCreator` in Gson terms that I'm
more familiar
On Wed, Aug 15, 2018 at 5:05 AM, Lyubomyr Shaydariv
wrote:
> Thanks for the reply, Tatu.
>
> Unfortunately, 2.6.7 works exactly the same like 2.6.3 does. However, if I
> switch to 2.9.6 (and I hope I'll migrate the project I work at too), the
> output is slightly different: `class
Thanks for the reply, Tatu.
Unfortunately, 2.6.7 works exactly the same like 2.6.3 does. However, if I
switch to 2.9.6 (and I hope I'll migrate the project I work at too), the
output is slightly different: `class com.sun.proxy.$Proxy0`. The assertion
error is never thrown though.
On
On Tue, Aug 14, 2018 at 1:30 PM, Lyubomyr Shaydariv
wrote:
> Hello,
>
> I've faced with an issue where I need to work with dynamic proxies since I
> find them a very convenient way allowing to reduce the amount of code
> dramatically. Please consider the following code:
>
> interface IUserDto {
>
Hello,
I've faced with an issue where I need to work with dynamic proxies since I
find them a very convenient way allowing to reduce the amount of code
dramatically. Please consider the following code:
interface IUserDto {
@JsonProperty(value = "name", access = JsonProperty.Access.READ_ONLY)
Hey,
I'm upgrading to 2.9.6 from 2.8.4, and I've run into a snag. It seems like
jackson used to fail to deserialize "" and throw an exception, but now it
is happy to deserialize it as null. I can try to update all of the
callsites where we were relying on the previous behavior to check
