If the call is exactly as shown and version of Jackson relatively new,
this might be a bug. View information should be retained.
But it is possible this could be due to certain code constructs such
as calling `writeObject()` on `JsonGenerator`, which will result in
new `SerializerProvider` (context
I hope it's ok if I just provide a link to my question on SO:
https://stackoverflow.com/questions/53484875/jsonview-not-propagated-to-nested-custom-serializer
Otherwise I'll do better next time. ;-)
--
You received this message because you are subscribed to the Google Groups
"jackson-user" gro
Hi,
I am using jackson for serialization/deserialization
I have no problem with
- simple objects
- objects with circular reference and no inheritance.
But when the object implies inheritance and circular reference, the
deserialization fails.
For example : I have an abstract superclass A ,whi
Apologies for slow response. I think things looks like something
potentially useful, as sort of Builder for JsonNode-trees. I don't know if
it would fit within `jackson-databind`, so best way would probably be to
package it as an extension. It is not quite a module (so should not be
named such), bu
On Sat, Nov 24, 2018 at 12:10 PM wrote:
> Quite strangely, the JDK's GZip is winning vs these fancy compression
> algorithms:
>
> Json size: 2727kb
> Json time: 26.426ms
>
> Smile size: 1043kb
> Smile time: 20.366ms
>
> Compressed Smile size: 914kb
> Compressed Smile time: 20.678ms
>
> GZip size:
On Sat, Nov 24, 2018 at 2:17 PM wrote:
> Now I'm curious of smile combined with this LZ4 implementation
> https://github.com/lz4/lz4-java
> The time is pretty close and the compression is decent, what do you think
> I need to do to be able to decorate the *SmileFactory*?
>
In theory, should work
