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
One of more ambitious features of Jackson 1.x and 2.x has been ability to auto-detect format for a given input stream. It worked nicely for first 2 formats (json, smile), and has been extended for couple more; but has been proven difficult to support for many other formats (due to arguably design flaws on many binary formats; lack of signature or magic cookie).
Although incomplete support across all formats is not itself a fatal flaw (feature could be just used between formats where it is useful), there is non-trivial cost for maintaining support and implementations. But perhaps most importantly, it also imposes some complexity in the way ObjectMappers / ObjectReaders are used; and unless removed, prevents #1 (or requires significant new development to find a work-around).
For this reason, this feature will be remove from Jackson 3.0.
The text was updated successfully, but these errors were encountered:
cowtowncoder
changed the title
Remove dataformat-auto-detection functionality from jackson-core
Remove dataformat-auto-detection functionality
Sep 14, 2017
One of more ambitious features of Jackson 1.x and 2.x has been ability to auto-detect format for a given input stream. It worked nicely for first 2 formats (json, smile), and has been extended for couple more; but has been proven difficult to support for many other formats (due to arguably design flaws on many binary formats; lack of signature or magic cookie).
Although incomplete support across all formats is not itself a fatal flaw (feature could be just used between formats where it is useful), there is non-trivial cost for maintaining support and implementations. But perhaps most importantly, it also imposes some complexity in the way ObjectMappers / ObjectReaders are used; and unless removed, prevents #1 (or requires significant new development to find a work-around).
For this reason, this feature will be remove from Jackson 3.0.
The text was updated successfully, but these errors were encountered: