You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem with ObjectCodec is that it refers to general "factory" entity (like ObjectMapper), so to read/write anything it is necessary to create active instances, but ones that are not (as of Jackson 2.x) carried through processing pipeline. This means that new distinct contexts are created, which not only add overhead (which may or may not be big issue) but also remove possible settings that reader/writer would have, as well as any state (context attributes).
So for 3.0 let's replace codec abstraction with separate stateful abstractions, work that has already started. Essentially:
ObjectReadContext will be used both for accessing necessary reader (parser) configuration, overrides AND state of deserialization.
ObjectWriteContext will be used both for accessing writer (generator) configuration, overrides AND state of serialization process.
So far most of latter has been done; more work needed for replacing reader usage.
The text was updated successfully, but these errors were encountered:
Problem with
ObjectCodec
is that it refers to general "factory" entity (likeObjectMapper
), so to read/write anything it is necessary to create active instances, but ones that are not (as of Jackson 2.x) carried through processing pipeline. This means that new distinct contexts are created, which not only add overhead (which may or may not be big issue) but also remove possible settings that reader/writer would have, as well as any state (context attributes).So for 3.0 let's replace codec abstraction with separate stateful abstractions, work that has already started. Essentially:
ObjectReadContext
will be used both for accessing necessary reader (parser) configuration, overrides AND state of deserialization.ObjectWriteContext
will be used both for accessing writer (generator) configuration, overrides AND state of serialization process.So far most of latter has been done; more work needed for replacing reader usage.
The text was updated successfully, but these errors were encountered: