json - Jackson 1.x to 2.x and the meaning of backwards compatibility -


by necessity, need upgrade jackson 1.x 2.x. after reading notes on release, thought fine upgrade, long made necessary code changes:

http://wiki.fasterxml.com/jacksonrelease20

however, realized after-the-fact still need able deserialize data serialized 1.x versions in event have pre-upgrade data data flowing service, guaranteed happen.

is jackson 2.x suited or not? understand 2.x requires recompile, can still handle old serialized format?

so, case data serialized jackson 1, read jackson 2, shouldn't problem @ all, since both understand json format.

there possibility have customizations based on annotation , hierarchies, if case, supported in jackson 1, should supported in jackson 2 (this backwards compatibility plays role).

in remote case have can deserialized jackson 1, can still rolling upgrade in project, jackson guys did amazing job in scenario, changed packages name com.fasterxml.jackson old org.codehaus.jackson, means both version can live in classpath, allowing upgrade things based on priorities, or incrementally.

i have experience in 3 scenarios mentioned, since our projects used use jackson 1 , moved of them latest , greatest.

hope helps,

jose luis


Comments

Popular posts from this blog

c++ - Difference between pre and post decrement in recursive function argument -

php - Nothing but 'run(); ' when browsing to my local project, how do I fix this? -

php - How can I echo out this array? -